Index: /pbibuild/modules/pgadmin/copy-files =================================================================== --- /pbibuild/modules/pgadmin/copy-files (revision 1440) +++ /pbibuild/modules/pgadmin/copy-files (revision 1448) @@ -1,3 +1,2 @@ /usr/local/bin/pgadmin3 bin/ /usr/local/bin/pgagent bin/ -/usr/local/share/pgadmin3 share/ Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pg_settings.csv =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pg_settings.csv (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pg_settings.csv (revision 1448) @@ -0,0 +1,185 @@ +"name";"setting";"category";"short_desc";"extra_desc";"context";"vartype";"source";"min_val";"max_val" +"add_missing_from";"off";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Automatically adds missing table references to FROM clauses.";"";"user";"bool";"default";"";"" +"allow_system_table_mods";"off";"Developer Options";"Allows modifications of the structure of system tables.";"";"postmaster";"bool";"default";"";"" +"archive_command";"";"Write-Ahead Log / Settings";"Sets the shell command that will be called to archive a WAL file.";"";"sighup";"string";"default";"";"" +"archive_timeout";"0";"Write-Ahead Log / Settings";"Forces a switch to the next xlog file if a new file has not been started within N seconds.";"";"sighup";"integer";"default";"0";"2147483647" +"array_nulls";"on";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Enable input of NULL elements in arrays.";"When turned on, unquoted NULL in an array input value means a null value; otherwise it is taken literally.";"user";"bool";"default";"";"" +"authentication_timeout";"60";"Connections and Authentication / Security and Authentication";"Sets the maximum allowed time to complete client authentication.";"";"sighup";"integer";"default";"1";"600" +"autovacuum";"on";"Autovacuum";"Starts the autovacuum subprocess.";"";"sighup";"bool";"default";"";"" +"autovacuum_analyze_scale_factor";"0.1";"Autovacuum";"Number of tuple inserts, updates or deletes prior to analyze as a fraction of reltuples.";"";"sighup";"real";"default";"0";"100" +"autovacuum_analyze_threshold";"50";"Autovacuum";"Minimum number of tuple inserts, updates or deletes prior to analyze.";"";"sighup";"integer";"default";"0";"2147483647" +"autovacuum_freeze_max_age";"200000000";"Autovacuum";"Age at which to autovacuum a table to prevent transaction ID wraparound.";"";"postmaster";"integer";"default";"100000000";"2000000000" +"autovacuum_max_workers";"3";"Autovacuum";"Sets the maximum number of simultaneously running autovacuum worker processes.";"";"postmaster";"integer";"default";"1";"536870911" +"autovacuum_naptime";"60";"Autovacuum";"Time to sleep between autovacuum runs.";"";"sighup";"integer";"default";"1";"2147483" +"autovacuum_vacuum_cost_delay";"20";"Autovacuum";"Vacuum cost delay in milliseconds, for autovacuum.";"";"sighup";"integer";"default";"-1";"1000" +"autovacuum_vacuum_cost_limit";"-1";"Autovacuum";"Vacuum cost amount available before napping, for autovacuum.";"";"sighup";"integer";"default";"-1";"10000" +"autovacuum_vacuum_scale_factor";"0.2";"Autovacuum";"Number of tuple updates or deletes prior to vacuum as a fraction of reltuples.";"";"sighup";"real";"default";"0";"100" +"autovacuum_vacuum_threshold";"50";"Autovacuum";"Minimum number of tuple updates or deletes prior to vacuum.";"";"sighup";"integer";"default";"0";"2147483647" +"backslash_quote";"safe_encoding";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Sets whether ""\'"" is allowed in string literals.";"Valid values are ON, OFF, and SAFE_ENCODING.";"user";"string";"default";"";"" +"bgwriter_delay";"200";"Resource Usage";"Background writer sleep time between rounds.";"";"sighup";"integer";"default";"10";"10000" +"bgwriter_lru_maxpages";"100";"Resource Usage";"Background writer maximum number of LRU pages to flush per round.";"";"sighup";"integer";"default";"0";"1000" +"bgwriter_lru_multiplier";"2";"Resource Usage";"Background writer multiplier on average buffers to scan per round.";"";"sighup";"real";"default";"0";"10" +"block_size";"8192";"Preset Options";"Shows the size of a disk block.";"";"internal";"integer";"default";"8192";"8192" +"bonjour_name";"";"Connections and Authentication / Connection Settings";"Sets the Bonjour broadcast service name.";"";"postmaster";"string";"default";"";"" +"check_function_bodies";"on";"Client Connection Defaults / Statement Behavior";"Check function bodies during CREATE FUNCTION.";"";"user";"bool";"default";"";"" +"checkpoint_completion_target";"0.5";"Write-Ahead Log / Checkpoints";"Time spent flushing dirty buffers during checkpoint, as fraction of checkpoint interval.";"";"sighup";"real";"default";"0";"1" +"checkpoint_segments";"3";"Write-Ahead Log / Checkpoints";"Sets the maximum distance in log segments between automatic WAL checkpoints.";"";"sighup";"integer";"default";"1";"2147483647" +"checkpoint_timeout";"300";"Write-Ahead Log / Checkpoints";"Sets the maximum time between automatic WAL checkpoints.";"";"sighup";"integer";"default";"30";"3600" +"checkpoint_warning";"30";"Write-Ahead Log / Checkpoints";"Enables warnings if checkpoint segments are filled more frequently than this.";"Write a message to the server log if checkpoints caused by the filling of checkpoint segment files happens more frequently than this number of seconds. Zero turns off the warning.";"sighup";"integer";"default";"0";"2147483647" +"client_encoding";"SQL_ASCII";"Client Connection Defaults / Locale and Formatting";"Sets the client's character set encoding.";"";"user";"string";"session";"";"" +"client_min_messages";"notice";"Reporting and Logging / When to Log";"Sets the message levels that are sent to the client.";"Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, LOG, NOTICE, WARNING, and ERROR. Each level includes all the levels that follow it. The later the level, the fewer messages are sent.";"user";"string";"default";"";"" +"commit_delay";"0";"Write-Ahead Log / Settings";"Sets the delay in microseconds between transaction commit and flushing WAL to disk.";"";"user";"integer";"default";"0";"100000" +"commit_siblings";"5";"Write-Ahead Log / Settings";"Sets the minimum concurrent open transactions before performing commit_delay.";"";"user";"integer";"default";"1";"1000" +"config_file";"C:/pgsql-8.3/data/postgresql.conf";"File Locations";"Sets the server's main configuration file.";"";"postmaster";"string";"override";"";"" +"constraint_exclusion";"off";"Query Tuning / Other Planner Options";"Enables the planner to use constraints to optimize queries.";"Child table scans will be skipped if their constraints guarantee that no rows match the query.";"user";"bool";"default";"";"" +"cpu_index_tuple_cost";"0.005";"Query Tuning / Planner Cost Constants";"Sets the planner's estimate of the cost of processing each index entry during an index scan.";"";"user";"real";"default";"0";"1.79769e+308" +"cpu_operator_cost";"0.0025";"Query Tuning / Planner Cost Constants";"Sets the planner's estimate of the cost of processing each operator or function call.";"";"user";"real";"default";"0";"1.79769e+308" +"cpu_tuple_cost";"0.01";"Query Tuning / Planner Cost Constants";"Sets the planner's estimate of the cost of processing each tuple (row).";"";"user";"real";"default";"0";"1.79769e+308" +"custom_variable_classes";"";"Customized Options";"Sets the list of known custom variable classes.";"";"sighup";"string";"default";"";"" +"data_directory";"C:/pgsql-8.3/data";"File Locations";"Sets the server's data directory.";"";"postmaster";"string";"override";"";"" +"DateStyle";"ISO, DMY";"Client Connection Defaults / Locale and Formatting";"Sets the display format for date and time values.";"Also controls interpretation of ambiguous date inputs.";"user";"string";"session";"";"" +"db_user_namespace";"off";"Connections and Authentication / Security and Authentication";"Enables per-database user names.";"";"sighup";"bool";"default";"";"" +"deadlock_timeout";"1000";"Lock Management";"Sets the time to wait on a lock before checking for deadlock.";"";"sighup";"integer";"default";"1";"2147483" +"debug_assertions";"on";"Developer Options";"Turns on various assertion checks.";"This is a debugging aid.";"user";"bool";"default";"";"" +"debug_pretty_print";"off";"Reporting and Logging / What to Log";"Indents parse and plan tree displays.";"";"user";"bool";"default";"";"" +"debug_print_parse";"off";"Reporting and Logging / What to Log";"Prints the parse tree to the server log.";"";"user";"bool";"default";"";"" +"debug_print_plan";"off";"Reporting and Logging / What to Log";"Prints the execution plan to server log.";"";"user";"bool";"default";"";"" +"debug_print_rewritten";"off";"Reporting and Logging / What to Log";"Prints the parse tree after rewriting to server log.";"";"user";"bool";"default";"";"" +"default_statistics_target";"10";"Query Tuning / Other Planner Options";"Sets the default statistics target.";"This applies to table columns that have not had a column-specific target set via ALTER TABLE SET STATISTICS.";"user";"integer";"default";"1";"1000" +"default_tablespace";"";"Client Connection Defaults / Statement Behavior";"Sets the default tablespace to create tables and indexes in.";"An empty string selects the database's default tablespace.";"user";"string";"default";"";"" +"default_text_search_config";"pg_catalog.simple";"Client Connection Defaults / Locale and Formatting";"Sets default text search configuration.";"";"user";"string";"configuration file";"";"" +"default_transaction_isolation";"read committed";"Client Connection Defaults / Statement Behavior";"Sets the transaction isolation level of each new transaction.";"Each SQL transaction has an isolation level, which can be either ""read uncommitted"", ""read committed"", ""repeatable read"", or ""serializable"".";"user";"string";"default";"";"" +"default_transaction_read_only";"off";"Client Connection Defaults / Statement Behavior";"Sets the default read-only status of new transactions.";"";"user";"bool";"default";"";"" +"default_with_oids";"off";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Create new tables with OIDs by default.";"";"user";"bool";"default";"";"" +"dynamic_library_path";"$libdir";"Client Connection Defaults / Other Defaults";"Sets the path for dynamically loadable modules.";"If a dynamically loadable module needs to be opened and the specified name does not have a directory component (i.e., the name does not contain a slash), the system will search this path for the specified file.";"superuser";"string";"default";"";"" +"effective_cache_size";"16384";"Query Tuning / Planner Cost Constants";"Sets the planner's assumption about the size of the disk cache.";"That is, the portion of the kernel's disk cache that will be used for PostgreSQL data files. This is measured in disk pages, which are normally 8 kB each.";"user";"integer";"default";"1";"2147483647" +"enable_bitmapscan";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of bitmap-scan plans.";"";"user";"bool";"default";"";"" +"enable_hashagg";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of hashed aggregation plans.";"";"user";"bool";"default";"";"" +"enable_hashjoin";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of hash join plans.";"";"user";"bool";"default";"";"" +"enable_indexscan";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of index-scan plans.";"";"user";"bool";"default";"";"" +"enable_mergejoin";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of merge join plans.";"";"user";"bool";"default";"";"" +"enable_nestloop";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of nested-loop join plans.";"";"user";"bool";"default";"";"" +"enable_seqscan";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of sequential-scan plans.";"";"user";"bool";"default";"";"" +"enable_sort";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of explicit sort steps.";"";"user";"bool";"default";"";"" +"enable_tidscan";"on";"Query Tuning / Planner Method Configuration";"Enables the planner's use of TID scan plans.";"";"user";"bool";"default";"";"" +"escape_string_warning";"on";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Warn about backslash escapes in ordinary string literals.";"";"user";"bool";"default";"";"" +"explain_pretty_print";"on";"Client Connection Defaults / Other Defaults";"Uses the indented output format for EXPLAIN VERBOSE.";"";"user";"bool";"default";"";"" +"external_pid_file";"";"File Locations";"Writes the postmaster PID to the specified file.";"";"postmaster";"string";"default";"";"" +"extra_float_digits";"0";"Client Connection Defaults / Locale and Formatting";"Sets the number of digits displayed for floating-point values.";"This affects real, double precision, and geometric data types. The parameter value is added to the standard number of digits (FLT_DIG or DBL_DIG as appropriate).";"user";"integer";"default";"-15";"2" +"from_collapse_limit";"8";"Query Tuning / Other Planner Options";"Sets the FROM-list size beyond which subqueries are not collapsed.";"The planner will merge subqueries into upper queries if the resulting FROM list would have no more than this many items.";"user";"integer";"default";"1";"2147483647" +"fsync";"on";"Write-Ahead Log / Settings";"Forces synchronization of updates to disk.";"The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash.";"sighup";"bool";"default";"";"" +"full_page_writes";"on";"Write-Ahead Log / Settings";"Writes full pages to WAL when first modified after a checkpoint.";"A page write in process during an operating system crash might be only partially written to disk. During recovery, the row changes stored in WAL are not enough to recover. This option writes pages when first modified after a checkpoint to WAL so full recovery is possible.";"sighup";"bool";"default";"";"" +"geqo";"on";"Query Tuning / Genetic Query Optimizer";"Enables genetic query optimization.";"This algorithm attempts to do planning without exhaustive searching.";"user";"bool";"default";"";"" +"geqo_effort";"5";"Query Tuning / Genetic Query Optimizer";"GEQO: effort is used to set the default for other GEQO parameters.";"";"user";"integer";"default";"1";"10" +"geqo_generations";"0";"Query Tuning / Genetic Query Optimizer";"GEQO: number of iterations of the algorithm.";"Zero selects a suitable default value.";"user";"integer";"default";"0";"2147483647" +"geqo_pool_size";"0";"Query Tuning / Genetic Query Optimizer";"GEQO: number of individuals in the population.";"Zero selects a suitable default value.";"user";"integer";"default";"0";"2147483647" +"geqo_selection_bias";"2";"Query Tuning / Genetic Query Optimizer";"GEQO: selective pressure within the population.";"";"user";"real";"default";"1.5";"2" +"geqo_threshold";"12";"Query Tuning / Genetic Query Optimizer";"Sets the threshold of FROM items beyond which GEQO is used.";"";"user";"integer";"default";"2";"2147483647" +"gin_fuzzy_search_limit";"0";"Client Connection Defaults / Other Defaults";"Sets the maximum allowed result for exact search by GIN.";"";"user";"integer";"default";"0";"2147483647" +"hba_file";"C:/pgsql-8.3/data/pg_hba.conf";"File Locations";"Sets the server's ""hba"" configuration file.";"";"postmaster";"string";"override";"";"" +"ident_file";"C:/pgsql-8.3/data/pg_ident.conf";"File Locations";"Sets the server's ""ident"" configuration file.";"";"postmaster";"string";"override";"";"" +"ignore_system_indexes";"off";"Developer Options";"Disables reading from system indexes.";"It does not prevent updating the indexes, so it is safe to use. The worst consequence is slowness.";"backend";"bool";"default";"";"" +"integer_datetimes";"on";"Preset Options";"Datetimes are integer based.";"";"internal";"bool";"default";"";"" +"join_collapse_limit";"8";"Query Tuning / Other Planner Options";"Sets the FROM-list size beyond which JOIN constructs are not flattened.";"The planner will flatten explicit JOIN constructs into lists of FROM items whenever a list of no more than this many items would result.";"user";"integer";"default";"1";"2147483647" +"krb_caseins_users";"off";"Connections and Authentication / Security and Authentication";"Sets whether Kerberos and GSSAPI user names should be treated as case-insensitive.";"";"postmaster";"bool";"default";"";"" +"krb_server_hostname";"";"Connections and Authentication / Security and Authentication";"Sets the hostname of the Kerberos server.";"";"postmaster";"string";"default";"";"" +"krb_server_keyfile";"";"Connections and Authentication / Security and Authentication";"Sets the location of the Kerberos server key file.";"";"postmaster";"string";"default";"";"" +"krb_srvname";"postgres";"Connections and Authentication / Security and Authentication";"Sets the name of the Kerberos service.";"";"postmaster";"string";"default";"";"" +"lc_collate";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Shows the collation order locale.";"";"internal";"string";"override";"";"" +"lc_ctype";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Shows the character classification and case conversion locale.";"";"internal";"string";"override";"";"" +"lc_messages";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Sets the language in which messages are displayed.";"";"superuser";"string";"configuration file";"";"" +"lc_monetary";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Sets the locale for formatting monetary amounts.";"";"user";"string";"configuration file";"";"" +"lc_numeric";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Sets the locale for formatting numbers.";"";"user";"string";"configuration file";"";"" +"lc_time";"English_United Kingdom.1252";"Client Connection Defaults / Locale and Formatting";"Sets the locale for formatting date and time values.";"";"user";"string";"configuration file";"";"" +"listen_addresses";"localhost";"Connections and Authentication / Connection Settings";"Sets the host name or IP address(es) to listen to.";"";"postmaster";"string";"default";"";"" +"local_preload_libraries";"";"Client Connection Defaults / Other Defaults";"Lists shared libraries to preload into each backend.";"";"backend";"string";"default";"";"" +"log_autovacuum_min_duration";"-1";"Reporting and Logging / What to Log";"Sets the minimum execution time above which autovacuum actions will be logged.";"Zero prints all actions. -1 turns autovacuum logging off.";"sighup";"integer";"default";"-1";"2147483" +"log_checkpoints";"off";"Reporting and Logging / What to Log";"Logs each checkpoint.";"";"sighup";"bool";"default";"";"" +"log_connections";"off";"Reporting and Logging / What to Log";"Logs each successful connection.";"";"backend";"bool";"default";"";"" +"log_destination";"stderr";"Reporting and Logging / Where to Log";"Sets the destination for server log output.";"Valid values are combinations of ""stderr"", ""syslog"", ""csvlog"", and ""eventlog"", depending on the platform.";"sighup";"string";"default";"";"" +"log_directory";"pg_log";"Reporting and Logging / Where to Log";"Sets the destination directory for log files.";"Can be specified as relative to the data directory or as absolute path.";"sighup";"string";"default";"";"" +"log_disconnections";"off";"Reporting and Logging / What to Log";"Logs end of a session, including duration.";"";"backend";"bool";"default";"";"" +"log_duration";"off";"Reporting and Logging / What to Log";"Logs the duration of each completed SQL statement.";"";"superuser";"bool";"default";"";"" +"log_error_verbosity";"default";"Reporting and Logging / When to Log";"Sets the verbosity of logged messages.";"Valid values are ""terse"", ""default"", and ""verbose"".";"superuser";"string";"default";"";"" +"log_executor_stats";"off";"Statistics / Monitoring";"Writes executor performance statistics to the server log.";"";"superuser";"bool";"default";"";"" +"log_filename";"postgresql-%Y-%m-%d_%H%M%S.log";"Reporting and Logging / Where to Log";"Sets the file name pattern for log files.";"";"sighup";"string";"default";"";"" +"log_hostname";"off";"Reporting and Logging / What to Log";"Logs the host name in the connection logs.";"By default, connection logs only show the IP address of the connecting host. If you want them to show the host name you can turn this on, but depending on your host name resolution setup it might impose a non-negligible performance penalty.";"sighup";"bool";"default";"";"" +"log_line_prefix";"";"Reporting and Logging / What to Log";"Controls information prefixed to each log line.";"If blank, no prefix is used.";"sighup";"string";"default";"";"" +"log_lock_waits";"off";"Reporting and Logging / What to Log";"Logs long lock waits.";"";"superuser";"bool";"default";"";"" +"log_min_duration_statement";"-1";"Reporting and Logging / When to Log";"Sets the minimum execution time above which statements will be logged.";"Zero prints all queries. -1 turns this feature off.";"superuser";"integer";"default";"-1";"2147483" +"log_min_error_statement";"error";"Reporting and Logging / When to Log";"Causes all statements generating error at or above this level to be logged.";"All SQL statements that cause an error of the specified level or a higher level are logged.";"superuser";"string";"default";"";"" +"log_min_messages";"notice";"Reporting and Logging / When to Log";"Sets the message levels that are logged.";"Valid values are DEBUG5, DEBUG4, DEBUG3, DEBUG2, DEBUG1, INFO, NOTICE, WARNING, ERROR, LOG, FATAL, and PANIC. Each level includes all the levels that follow it.";"superuser";"string";"default";"";"" +"log_parser_stats";"off";"Statistics / Monitoring";"Writes parser performance statistics to the server log.";"";"superuser";"bool";"default";"";"" +"log_planner_stats";"off";"Statistics / Monitoring";"Writes planner performance statistics to the server log.";"";"superuser";"bool";"default";"";"" +"log_rotation_age";"1440";"Reporting and Logging / Where to Log";"Automatic log file rotation will occur after N minutes.";"";"sighup";"integer";"default";"0";"35791394" +"log_rotation_size";"10240";"Reporting and Logging / Where to Log";"Automatic log file rotation will occur after N kilobytes.";"";"sighup";"integer";"default";"0";"2097151" +"log_statement";"none";"Reporting and Logging / What to Log";"Sets the type of statements logged.";"Valid values are ""none"", ""ddl"", ""mod"", and ""all"".";"superuser";"string";"default";"";"" +"log_statement_stats";"off";"Statistics / Monitoring";"Writes cumulative performance statistics to the server log.";"";"superuser";"bool";"default";"";"" +"log_temp_files";"-1";"Reporting and Logging / What to Log";"Log the use of temporary files larger than this number of kilobytes.";"Zero logs all files. The default is -1 (turning this feature off).";"user";"integer";"default";"-1";"2147483647" +"log_timezone";"Europe/London";"Reporting and Logging / What to Log";"Sets the time zone to use in log messages.";"";"sighup";"string";"command line";"";"" +"log_truncate_on_rotation";"off";"Reporting and Logging / Where to Log";"Truncate existing log files of same name during log rotation.";"";"sighup";"bool";"default";"";"" +"logging_collector";"on";"Reporting and Logging / Where to Log";"Start a subprocess to capture stderr output and/or csvlogs into log files.";"";"postmaster";"bool";"configuration file";"";"" +"maintenance_work_mem";"16384";"Resource Usage / Memory";"Sets the maximum memory to be used for maintenance operations.";"This includes operations such as VACUUM and CREATE INDEX.";"user";"integer";"default";"1024";"2097151" +"max_connections";"100";"Connections and Authentication / Connection Settings";"Sets the maximum number of concurrent connections.";"";"postmaster";"integer";"configuration file";"1";"536870911" +"max_files_per_process";"1000";"Resource Usage / Kernel Resources";"Sets the maximum number of simultaneously open files for each server process.";"";"postmaster";"integer";"default";"25";"2147483647" +"max_fsm_pages";"204800";"Resource Usage / Free Space Map";"Sets the maximum number of disk pages for which free space is tracked.";"";"postmaster";"integer";"configuration file";"1000";"2147483647" +"max_fsm_relations";"1000";"Resource Usage / Free Space Map";"Sets the maximum number of tables and indexes for which free space is tracked.";"";"postmaster";"integer";"default";"100";"2147483647" +"max_function_args";"100";"Preset Options";"Shows the maximum number of function arguments.";"";"internal";"integer";"default";"100";"100" +"max_identifier_length";"63";"Preset Options";"Shows the maximum identifier length.";"";"internal";"integer";"default";"63";"63" +"max_index_keys";"32";"Preset Options";"Shows the maximum number of index keys.";"";"internal";"integer";"default";"32";"32" +"max_locks_per_transaction";"64";"Lock Management";"Sets the maximum number of locks per transaction.";"The shared lock table is sized on the assumption that at most max_locks_per_transaction * max_connections distinct objects will need to be locked at any one time.";"postmaster";"integer";"default";"10";"2147483647" +"max_prepared_transactions";"5";"Resource Usage";"Sets the maximum number of simultaneously prepared transactions.";"";"postmaster";"integer";"default";"0";"2147483647" +"max_stack_depth";"2048";"Resource Usage / Memory";"Sets the maximum stack depth, in kilobytes.";"";"superuser";"integer";"environment variable";"100";"2097151" +"password_encryption";"on";"Connections and Authentication / Security and Authentication";"Encrypt passwords.";"When a password is specified in CREATE USER or ALTER USER without writing either ENCRYPTED or UNENCRYPTED, this parameter determines whether the password is to be encrypted.";"user";"bool";"default";"";"" +"port";"5433";"Connections and Authentication / Connection Settings";"Sets the TCP port the server listens on.";"";"postmaster";"integer";"configuration file";"1";"65535" +"post_auth_delay";"0";"Developer Options";"Waits N seconds on connection startup after authentication.";"This allows attaching a debugger to the process.";"backend";"integer";"default";"0";"2147483647" +"pre_auth_delay";"0";"Developer Options";"Waits N seconds on connection startup before authentication.";"This allows attaching a debugger to the process.";"sighup";"integer";"default";"0";"60" +"random_page_cost";"4";"Query Tuning / Planner Cost Constants";"Sets the planner's estimate of the cost of a nonsequentially fetched disk page.";"";"user";"real";"default";"0";"1.79769e+308" +"regex_flavor";"advanced";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Sets the regular expression ""flavor"".";"This can be set to advanced, extended, or basic.";"user";"string";"default";"";"" +"search_path";"""$user"",public";"Client Connection Defaults / Statement Behavior";"Sets the schema search order for names that are not schema-qualified.";"";"user";"string";"default";"";"" +"seq_page_cost";"1";"Query Tuning / Planner Cost Constants";"Sets the planner's estimate of the cost of a sequentially fetched disk page.";"";"user";"real";"default";"0";"1.79769e+308" +"server_encoding";"SQL_ASCII";"Client Connection Defaults / Locale and Formatting";"Sets the server (database) character set encoding.";"";"internal";"string";"override";"";"" +"server_version";"8.3devel";"Preset Options";"Shows the server version.";"";"internal";"string";"default";"";"" +"server_version_num";"80300";"Preset Options";"Shows the server version as an integer.";"";"internal";"integer";"default";"80300";"80300" +"session_replication_role";"origin";"Client Connection Defaults / Statement Behavior";"Sets the sessions behavior for triggers and rewrite rules.";"Each session can be either ""origin"", ""replica"" or ""local"".";"superuser";"string";"default";"";"" +"shared_buffers";"4096";"Resource Usage / Memory";"Sets the number of shared memory buffers used by the server.";"";"postmaster";"integer";"configuration file";"16";"1073741823" +"shared_preload_libraries";"";"Resource Usage / Kernel Resources";"Lists shared libraries to preload into server.";"";"postmaster";"string";"default";"";"" +"silent_mode";"off";"Reporting and Logging / When to Log";"Runs the server silently.";"If this parameter is set, the server will automatically run in the background and any controlling terminals are dissociated.";"postmaster";"bool";"default";"";"" +"sql_inheritance";"on";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Causes subtables to be included by default in various commands.";"";"user";"bool";"default";"";"" +"ssl";"off";"Connections and Authentication / Security and Authentication";"Enables SSL connections.";"";"postmaster";"bool";"configuration file";"";"" +"ssl_ciphers";"ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH";"Connections and Authentication / Security and Authentication";"Sets the list of allowed SSL ciphers.";"";"postmaster";"string";"default";"";"" +"standard_conforming_strings";"off";"Version and Platform Compatibility / Previous PostgreSQL Versions";"Causes '...' strings to treat backslashes literally.";"";"user";"bool";"default";"";"" +"statement_timeout";"0";"Client Connection Defaults / Statement Behavior";"Sets the maximum allowed duration of any statement.";"A value of 0 turns off the timeout.";"user";"integer";"default";"0";"2147483647" +"superuser_reserved_connections";"3";"Connections and Authentication / Connection Settings";"Sets the number of connection slots reserved for superusers.";"";"postmaster";"integer";"default";"0";"536870911" +"synchronous_commit";"on";"Write-Ahead Log / Settings";"Sets immediate fsync at commit.";"";"user";"bool";"default";"";"" +"tcp_keepalives_count";"0";"Client Connection Defaults / Other Defaults";"Maximum number of TCP keepalive retransmits.";"This controls the number of consecutive keepalive retransmits that can be lost before a connection is considered dead. A value of 0 uses the system default.";"user";"integer";"default";"0";"2147483647" +"tcp_keepalives_idle";"0";"Client Connection Defaults / Other Defaults";"Time between issuing TCP keepalives.";"A value of 0 uses the system default.";"user";"integer";"default";"0";"2147483647" +"tcp_keepalives_interval";"0";"Client Connection Defaults / Other Defaults";"Time between TCP keepalive retransmits.";"A value of 0 uses the system default.";"user";"integer";"default";"0";"2147483647" +"temp_buffers";"1024";"Resource Usage / Memory";"Sets the maximum number of temporary buffers used by each session.";"";"user";"integer";"default";"100";"1073741823" +"temp_tablespaces";"";"Client Connection Defaults / Statement Behavior";"Sets the tablespace(s) to use for temporary tables and sort files.";"";"user";"string";"default";"";"" +"TimeZone";"Europe/London";"Client Connection Defaults / Locale and Formatting";"Sets the time zone for displaying and interpreting time stamps.";"";"user";"string";"command line";"";"" +"timezone_abbreviations";"Default";"Client Connection Defaults / Locale and Formatting";"Selects a file of time zone abbreviations.";"";"user";"string";"command line";"";"" +"trace_notify";"off";"Developer Options";"Generates debugging output for LISTEN and NOTIFY.";"";"user";"bool";"default";"";"" +"trace_sort";"off";"Developer Options";"Emit information about resource usage in sorting.";"";"user";"bool";"default";"";"" +"track_activities";"on";"Statistics / Query and Index Statistics Collector";"Collects information about executing commands.";"Enables the collection of information on the currently executing command of each session, along with the time at which that command began execution.";"superuser";"bool";"default";"";"" +"track_counts";"on";"Statistics / Query and Index Statistics Collector";"Collects statistics on database activity.";"";"superuser";"bool";"default";"";"" +"transaction_isolation";"read committed";"Client Connection Defaults / Statement Behavior";"Sets the current transaction's isolation level.";"";"user";"string";"override";"";"" +"transaction_read_only";"off";"Client Connection Defaults / Statement Behavior";"Sets the current transaction's read-only status.";"";"user";"bool";"override";"";"" +"transform_null_equals";"off";"Version and Platform Compatibility / Other Platforms and Clients";"Treats ""expr=NULL"" as ""expr IS NULL"".";"When turned on, expressions of the form expr = NULL (or NULL = expr) are treated as expr IS NULL, that is, they return true if expr evaluates to the null value, and false otherwise. The correct behavior of expr = NULL is to always return null (unknown).";"user";"bool";"default";"";"" +"unix_socket_directory";"";"Connections and Authentication / Connection Settings";"Sets the directory where the Unix-domain socket will be created.";"";"postmaster";"string";"default";"";"" +"unix_socket_group";"";"Connections and Authentication / Connection Settings";"Sets the owning group of the Unix-domain socket.";"The owning user of the socket is always the user that starts the server.";"postmaster";"string";"default";"";"" +"unix_socket_permissions";"511";"Connections and Authentication / Connection Settings";"Sets the access permissions of the Unix-domain socket.";"Unix-domain sockets use the usual Unix file system permission set. The parameter value is expected to be an numeric mode specification in the form accepted by the chmod and umask system calls. (To use the customary octal format the number must start with a 0 (zero).)";"postmaster";"integer";"default";"0";"511" +"update_process_title";"on";"Statistics / Query and Index Statistics Collector";"Updates the process title to show the active SQL command.";"Enables updating of the process title every time a new SQL command is received by the server.";"superuser";"bool";"default";"";"" +"vacuum_cost_delay";"0";"Resource Usage";"Vacuum cost delay in milliseconds.";"";"user";"integer";"default";"0";"1000" +"vacuum_cost_limit";"200";"Resource Usage";"Vacuum cost amount available before napping.";"";"user";"integer";"default";"1";"10000" +"vacuum_cost_page_dirty";"20";"Resource Usage";"Vacuum cost for a page dirtied by vacuum.";"";"user";"integer";"default";"0";"10000" +"vacuum_cost_page_hit";"1";"Resource Usage";"Vacuum cost for a page found in the buffer cache.";"";"user";"integer";"default";"0";"10000" +"vacuum_cost_page_miss";"10";"Resource Usage";"Vacuum cost for a page not found in the buffer cache.";"";"user";"integer";"default";"0";"10000" +"vacuum_freeze_min_age";"100000000";"Client Connection Defaults / Statement Behavior";"Minimum age at which VACUUM should freeze a table row.";"";"user";"integer";"default";"0";"1000000000" +"wal_buffers";"8";"Write-Ahead Log / Settings";"Sets the number of disk-page buffers in shared memory for WAL.";"";"postmaster";"integer";"default";"4";"2147483647" +"wal_sync_method";"open_datasync";"Write-Ahead Log / Settings";"Selects the method used for forcing WAL updates to disk.";"";"sighup";"string";"default";"";"" +"wal_writer_delay";"200";"Write-Ahead Log / Settings";"WAL writer sleep time between WAL flushes.";"";"sighup";"integer";"default";"1";"10000" +"work_mem";"1024";"Resource Usage / Memory";"Sets the maximum memory to be used for query workspaces.";"This much memory can be used by each internal sort operation and hash table before switching to temporary disk files.";"user";"integer";"default";"64";"2097151" +"xmlbinary";"base64";"Client Connection Defaults / Statement Behavior";"Sets how binary values are to be encoded in XML.";"Valid values are BASE64 and HEX.";"user";"string";"default";"";"" +"xmloption";"content";"Client Connection Defaults / Statement Behavior";"Sets whether XML data in implicit parsing and serialization operations is to be considered as documents or content fragments.";"Valid values are DOCUMENT and CONTENT.";"user";"string";"default";"";"" +"zero_damaged_pages";"off";"Developer Options";"Continues processing past damaged page headers.";"Detection of a damaged page header normally causes PostgreSQL to report an error, aborting the current transaction. Setting zero_damaged_pages to true causes the system to instead report a warning, zero out the damaged page, and continue processing. This behavior will destroy data, namely all the rows on the damaged page.";"superuser";"bool";"default";"";"" Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pgadmin3.lng =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pgadmin3.lng (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/i18n/pgadmin3.lng (revision 1448) @@ -0,0 +1,64 @@ +########################################################################## +# +# pgAdmin III - PostgreSQL Tools +# Copyright (C) 2002 - 2006, The pgAdmin Development Team +# This software is released under the Artistic Licence +# +# pgadmin3.lng - Language names for language selection +# +# - first column contains precise name to match wxWindow's name +# - second column contains translated name in the native language +# - separated by Comma +# - surrounding spaces are removed +# - this file is interpreted UTF-8 +# +########################################################################## + +Afrikaans, Afrikaans +Arabic (Saudi Arabia), العربية +Arabic, العربيّة +Bulgarian, Български +Chinese (Simplified), 中文 (简体) +Chinese (Traditional), 中文 (正體) +Catalan, Català +Czech, Czech +Croatian, Hrvatski +Danish, Dansk +Dutch, Nederlands +English (U.S.), English +Farsi, فارسی +Finnish, Suomi +French, Français +Galician, Galego +German, Deutsch +German (Swiss), Deutsch (Schweiz) +Greek, Ελληνικά +Gujarati, Gujarati +Hindi, Hindi +Hungarian, Magyar +Indonesian, Indonesia +Icelandic, Icelandic +Italian, Italiano +Japanese, 日本 +Korean, Korean +Latvian, Latviešu +Lithuanian, Lietuviskai +Macedonian, Македонски +Norwegian (Bokmal), Norwegian (Bokmal) +Polish, Polski +Portuguese, Português +Portuguese (Brazilian), Português (Brasileiro) +Romanian, Romana +Russian, Русский +Serbian (Cyrillic), Српски +Sindhi, Sindhi +Slovenian, Slovenščina +Slovak, Slovensky +Spanish, Spanish +Swedish, Svenska +Tagalog (Philippines), Tagalog +Telugu, Telugu +Turkish, Türkçe +Ukrainian, Українська +Urdu (Pakistan), Urdu +Vietnamese, tiếng Việt Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/pgagent.sql =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/pgagent.sql (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/pgagent.sql (revision 1448) @@ -0,0 +1,649 @@ +/* +// pgAgent - PostgreSQL Tools +// $Id: pgagent.sql 6750 2007-10-16 09:37:05Z dpage $ +// Copyright (C) 2002 - 2006 The pgAdmin Development Team +// This software is released under the Artistic Licence +// +// pgagent.sql - pgAgent tables and functions +// +*/ + +BEGIN TRANSACTION; + + + +CREATE SCHEMA pgagent; +COMMENT ON SCHEMA pgagent IS 'pgAgent system tables'; + + + +CREATE TABLE pgagent.pga_jobagent ( +jagpid int4 NOT NULL PRIMARY KEY, +jaglogintime timestamptz NOT NULL DEFAULT current_timestamp, +jagstation text NOT NULL +) WITHOUT OIDS; +COMMENT ON TABLE pgagent.pga_jobagent IS 'Active job agents'; + + + +CREATE TABLE pgagent.pga_jobclass ( +jclid serial NOT NULL PRIMARY KEY, +jclname text NOT NULL +) WITHOUT OIDS; +CREATE UNIQUE INDEX pga_jobclass_name ON pgagent.pga_jobclass(jclname); +COMMENT ON TABLE pgagent.pga_jobclass IS 'Job classification'; + +INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Routine Maintenance'); +INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data Import'); +INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data Export'); +INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Data Summarisation'); +INSERT INTO pgagent.pga_jobclass (jclname) VALUES ('Miscellaneous'); + + + +CREATE TABLE pgagent.pga_job ( +jobid serial NOT NULL PRIMARY KEY, +jobjclid int4 NOT NULL REFERENCES pgagent.pga_jobclass (jclid) ON DELETE RESTRICT ON UPDATE RESTRICT, +jobname text NOT NULL, +jobdesc text NOT NULL DEFAULT '', +jobhostagent text NOT NULL DEFAULT '', +jobenabled bool NOT NULL DEFAULT true, +jobcreated timestamptz NOT NULL DEFAULT current_timestamp, +jobchanged timestamptz NOT NULL DEFAULT current_timestamp, +jobagentid int4 NULL REFERENCES pgagent.pga_jobagent(jagpid) ON DELETE SET NULL ON UPDATE RESTRICT, +jobnextrun timestamptz NULL, +joblastrun timestamptz NULL +) WITHOUT OIDS; +COMMENT ON TABLE pgagent.pga_job IS 'Job main entry'; +COMMENT ON COLUMN pgagent.pga_job.jobagentid IS 'Agent that currently executes this job.'; + + + +CREATE TABLE pgagent.pga_jobstep ( +jstid serial NOT NULL PRIMARY KEY, +jstjobid int4 NOT NULL REFERENCES pgagent.pga_job (jobid) ON DELETE CASCADE ON UPDATE RESTRICT, +jstname text NOT NULL, +jstdesc text NOT NULL DEFAULT '', +jstenabled bool NOT NULL DEFAULT true, +jstkind char NOT NULL CHECK (jstkind IN ('b', 's')), -- batch, sql +jstcode text NOT NULL, +jstdbname name NOT NULL DEFAULT '' CHECK ((jstdbname != '' AND jstkind = 's') OR (jstdbname = '' AND jstkind = 'b')), +jstonerror char NOT NULL CHECK (jstonerror IN ('f', 's', 'i')) DEFAULT 'f', -- fail, success, ignore +jscnextrun timestamptz NULL +) WITHOUT OIDS; +CREATE INDEX pga_jobstep_jobid ON pgagent.pga_jobstep(jstjobid); +COMMENT ON TABLE pgagent.pga_jobstep IS 'Job step to be executed'; +COMMENT ON COLUMN pgagent.pga_jobstep.jstkind IS 'Kind of jobstep: s=sql, b=batch'; +COMMENT ON COLUMN pgagent.pga_jobstep.jstonerror IS 'What to do if step returns an error: f=fail the job, s=mark step as succeeded and continue, i=mark as fail but ignore it and proceed'; + + + +CREATE TABLE pgagent.pga_schedule ( +jscid serial NOT NULL PRIMARY KEY, +jscjobid int4 NOT NULL REFERENCES pgagent.pga_job (jobid) ON DELETE CASCADE ON UPDATE RESTRICT, +jscname text NOT NULL, +jscdesc text NOT NULL DEFAULT '', +jscenabled bool NOT NULL DEFAULT true, +jscstart timestamptz NOT NULL DEFAULT current_timestamp, +jscend timestamptz NULL, +jscminutes bool[60] NOT NULL DEFAULT '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', +jschours bool[24] NOT NULL DEFAULT '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', +jscweekdays bool[7] NOT NULL DEFAULT '{f,f,f,f,f,f,f}', +jscmonthdays bool[32] NOT NULL DEFAULT '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', +jscmonths bool[12] NOT NULL DEFAULT '{f,f,f,f,f,f,f,f,f,f,f,f}', +CONSTRAINT pga_schedule_jscminutes_size CHECK (array_upper(jscminutes, 1) = 60), +CONSTRAINT pga_schedule_jschours_size CHECK (array_upper(jschours, 1) = 24), +CONSTRAINT pga_schedule_jscweekdays_size CHECK (array_upper(jscweekdays, 1) = 7), +CONSTRAINT pga_schedule_jscmonthdays_size CHECK (array_upper(jscmonthdays, 1) = 32), +CONSTRAINT pga_schedule_jscmonths_size CHECK (array_upper(jscmonths, 1) = 12) +) WITHOUT OIDS; +CREATE INDEX pga_jobschedule_jobid ON pgagent.pga_schedule(jscjobid); +COMMENT ON TABLE pgagent.pga_schedule IS 'Schedule for a job'; + + + +CREATE TABLE pgagent.pga_exception ( +jexid serial NOT NULL PRIMARY KEY, +jexscid int4 NOT NULL REFERENCES pgagent.pga_schedule (jscid) ON DELETE CASCADE ON UPDATE RESTRICT, +jexdate date NULL, +jextime time NULL +) +WITHOUT OIDS; +CREATE INDEX pga_exception_jexscid ON pgagent.pga_exception (jexscid); +CREATE UNIQUE INDEX pga_exception_datetime ON pgagent.pga_exception (jexdate, jextime); +COMMENT ON TABLE pgagent.pga_schedule IS 'Job schedule exceptions'; + + + +CREATE TABLE pgagent.pga_joblog ( +jlgid serial NOT NULL PRIMARY KEY, +jlgjobid int4 NOT NULL REFERENCES pgagent.pga_job (jobid) ON DELETE CASCADE ON UPDATE RESTRICT, +jlgstatus char NOT NULL CHECK (jlgstatus IN ('r', 's', 'f', 'i', 'd')) DEFAULT 'r', -- running, success, failed, internal failure, aborted +jlgstart timestamptz NOT NULL DEFAULT current_timestamp, +jlgduration interval NULL +) WITHOUT OIDS; +CREATE INDEX pga_joblog_jobid ON pgagent.pga_joblog(jlgjobid); +COMMENT ON TABLE pgagent.pga_joblog IS 'Job run logs.'; +COMMENT ON COLUMN pgagent.pga_joblog.jlgstatus IS 'Status of job: r=running, s=successfully finished, f=failed, i=no steps to execute, d=aborted'; + + + +CREATE TABLE pgagent.pga_jobsteplog ( +jslid serial NOT NULL PRIMARY KEY, +jsljlgid int4 NOT NULL REFERENCES pgagent.pga_joblog (jlgid) ON DELETE CASCADE ON UPDATE RESTRICT, +jsljstid int4 NOT NULL REFERENCES pgagent.pga_jobstep (jstid) ON DELETE CASCADE ON UPDATE RESTRICT, +jslstatus char NOT NULL CHECK (jslstatus IN ('r', 's', 'i', 'f', 'd')) DEFAULT 'r', -- running, success, ignored, failed, aborted +jslresult int2 NULL, +jslstart timestamptz NOT NULL DEFAULT current_timestamp, +jslduration interval NULL, +jsloutput text +) WITHOUT OIDS; +CREATE INDEX pga_jobsteplog_jslid ON pgagent.pga_jobsteplog(jsljlgid); +COMMENT ON TABLE pgagent.pga_jobsteplog IS 'Job step run logs.'; +COMMENT ON COLUMN pgagent.pga_jobsteplog.jslstatus IS 'Status of job step: r=running, s=successfully finished, f=failed stopping job, i=ignored failure, d=aborted'; +COMMENT ON COLUMN pgagent.pga_jobsteplog.jslresult IS 'Return code of job step'; + + + +CREATE OR REPLACE FUNCTION pgagent.pga_next_schedule(int4, timestamptz, timestamptz, _bool, _bool, _bool, _bool, _bool) RETURNS timestamptz AS ' +DECLARE + jscid ALIAS FOR $1; + jscstart ALIAS FOR $2; + jscend ALIAS FOR $3; + jscminutes ALIAS FOR $4; + jschours ALIAS FOR $5; + jscweekdays ALIAS FOR $6; + jscmonthdays ALIAS FOR $7; + jscmonths ALIAS FOR $8; + + nextrun timestamp := ''1970-01-01 00:00:00-00''; + runafter timestamp := ''1970-01-01 00:00:00-00''; + + bingo bool := FALSE; + gotit bool := FALSE; + foundval bool := FALSE; + daytweak bool := FALSE; + minutetweak bool := FALSE; + + i int2 := 0; + d int2 := 0; + + nextminute int2 := 0; + nexthour int2 := 0; + nextday int2 := 0; + nextmonth int2 := 0; + nextyear int2 := 0; + + +BEGIN + -- No valid start date has been specified + IF jscstart IS NULL THEN RETURN NULL; END IF; + + -- The schedule is past its end date + IF jscend IS NOT NULL AND jscend < now() THEN RETURN NULL; END IF; + + -- Get the time to find the next run after. It will just be the later of + -- now() + 1m and the start date for the time being, however, we might want to + -- do more complex things using this value in the future. + IF date_trunc(''MINUTE'', jscstart) > date_trunc(''MINUTE'', (now() + ''1 Minute''::interval)) THEN + runafter := date_trunc(''MINUTE'', jscstart); + ELSE + runafter := date_trunc(''MINUTE'', (now() + ''1 Minute''::interval)); + END IF; + + -- + -- Enter a loop, generating next run timestamps until we find one + -- that falls on the required weekday, and is not matched by an exception + -- + + WHILE bingo = FALSE LOOP + + -- + -- Get the next run year + -- + nextyear := date_part(''YEAR'', runafter); + + -- + -- Get the next run month + -- + nextmonth := date_part(''MONTH'', runafter); + gotit := FALSE; + FOR i IN (nextmonth) .. 12 LOOP + IF jscmonths[i] = TRUE THEN + nextmonth := i; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + IF gotit = FALSE THEN + FOR i IN 1 .. (nextmonth - 1) LOOP + IF jscmonths[i] = TRUE THEN + nextmonth := i; + + -- Wrap into next year + nextyear := nextyear + 1; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + END IF; + + -- + -- Get the next run day + -- + -- If the year, or month have incremented, get the lowest day, + -- otherwise look for the next day matching or after today. + IF (nextyear > date_part(''YEAR'', runafter) OR nextmonth > date_part(''MONTH'', runafter)) THEN + nextday := 1; + FOR i IN 1 .. 32 LOOP + IF jscmonthdays[i] = TRUE THEN + nextday := i; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + ELSE + nextday := date_part(''DAY'', runafter); + gotit := FALSE; + FOR i IN nextday .. 32 LOOP + IF jscmonthdays[i] = TRUE THEN + nextday := i; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + IF gotit = FALSE THEN + FOR i IN 1 .. (nextday - 1) LOOP + IF jscmonthdays[i] = TRUE THEN + nextday := i; + + -- Wrap into next month + IF nextmonth = 12 THEN + nextyear := nextyear + 1; + nextmonth := 1; + ELSE + nextmonth := nextmonth + 1; + END IF; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + END IF; + END IF; + + -- Was the last day flag selected? + IF nextday = 32 THEN + IF nextmonth = 1 THEN + nextday := 31; + ELSIF nextmonth = 2 THEN + IF pgagent.pga_is_leap_year(nextyear) = TRUE THEN + nextday := 29; + ELSE + nextday := 28; + END IF; + ELSIF nextmonth = 3 THEN + nextday := 31; + ELSIF nextmonth = 4 THEN + nextday := 30; + ELSIF nextmonth = 5 THEN + nextday := 31; + ELSIF nextmonth = 6 THEN + nextday := 30; + ELSIF nextmonth = 7 THEN + nextday := 31; + ELSIF nextmonth = 8 THEN + nextday := 31; + ELSIF nextmonth = 9 THEN + nextday := 30; + ELSIF nextmonth = 10 THEN + nextday := 31; + ELSIF nextmonth = 11 THEN + nextday := 30; + ELSIF nextmonth = 12 THEN + nextday := 31; + END IF; + END IF; + + -- + -- Get the next run hour + -- + -- If the year, month or day have incremented, get the lowest hour, + -- otherwise look for the next hour matching or after the current one. + IF (nextyear > date_part(''YEAR'', runafter) OR nextmonth > date_part(''MONTH'', runafter) OR nextday > date_part(''DAY'', runafter) OR daytweak = TRUE) THEN + nexthour := 0; + FOR i IN 1 .. 24 LOOP + IF jschours[i] = TRUE THEN + nexthour := i - 1; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + ELSE + nexthour := date_part(''HOUR'', runafter); + gotit := FALSE; + FOR i IN (nexthour + 1) .. 24 LOOP + IF jschours[i] = TRUE THEN + nexthour := i - 1; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + IF gotit = FALSE THEN + FOR i IN 1 .. nexthour LOOP + IF jschours[i] = TRUE THEN + nexthour := i - 1; + + -- Wrap into next month + IF (nextmonth = 1 OR nextmonth = 3 OR nextmonth = 5 OR nextmonth = 7 OR nextmonth = 8 OR nextmonth = 10 OR nextmonth = 12) THEN + d = 31; + ELSIF (nextmonth = 4 OR nextmonth = 6 OR nextmonth = 9 OR nextmonth = 11) THEN + d = 30; + ELSE + IF pgagent.pga_is_leap_year(nextyear) = TRUE THEN + d := 29; + ELSE + d := 28; + END IF; + END IF; + + IF nextday = d THEN + nextday := 1; + IF nextmonth = 12 THEN + nextyear := nextyear + 1; + nextmonth := 1; + ELSE + nextmonth := nextmonth + 1; + END IF; + ELSE + nextday := nextday + 1; + END IF; + + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + END IF; + END IF; + + -- + -- Get the next run minute + -- + -- If the year, month day or hour have incremented, get the lowest minute, + -- otherwise look for the next minute matching or after the current one. + IF (nextyear > date_part(''YEAR'', runafter) OR nextmonth > date_part(''MONTH'', runafter) OR nextday > date_part(''DAY'', runafter) OR nexthour > date_part(''HOUR'', runafter) OR daytweak = TRUE) THEN + nextminute := 0; + IF minutetweak = TRUE THEN + d := 1; + ELSE + d := date_part(''YEAR'', runafter)::int2; + END IF; + FOR i IN d .. 60 LOOP + IF jscminutes[i] = TRUE THEN + nextminute := i - 1; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + ELSE + nextminute := date_part(''MINUTE'', runafter); + gotit := FALSE; + FOR i IN (nextminute + 1) .. 60 LOOP + IF jscminutes[i] = TRUE THEN + nextminute := i - 1; + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + IF gotit = FALSE THEN + FOR i IN 1 .. nextminute LOOP + IF jscminutes[i] = TRUE THEN + nextminute := i - 1; + + -- Wrap into next hour + IF (nextmonth = 1 OR nextmonth = 3 OR nextmonth = 5 OR nextmonth = 7 OR nextmonth = 8 OR nextmonth = 10 OR nextmonth = 12) THEN + d = 31; + ELSIF (nextmonth = 4 OR nextmonth = 6 OR nextmonth = 9 OR nextmonth = 11) THEN + d = 30; + ELSE + IF pgagent.pga_is_leap_year(nextyear) = TRUE THEN + d := 29; + ELSE + d := 28; + END IF; + END IF; + + IF nexthour = 23 THEN + nexthour = 0; + IF nextday = d THEN + nextday := 1; + IF nextmonth = 12 THEN + nextyear := nextyear + 1; + nextmonth := 1; + ELSE + nextmonth := nextmonth + 1; + END IF; + ELSE + nextday := nextday + 1; + END IF; + ELSE + nexthour := nexthour + 1; + END IF; + + gotit := TRUE; + foundval := TRUE; + EXIT; + END IF; + END LOOP; + END IF; + END IF; + + -- Build the result, and check it is not the same as runafter - this may + -- happen if all array entries are set to false. In this case, add a minute. + + nextrun := (nextyear::varchar || ''-''::varchar || nextmonth::varchar || ''-'' || nextday::varchar || '' '' || nexthour::varchar || '':'' || nextminute::varchar)::timestamptz; + + IF nextrun = runafter AND foundval = FALSE THEN + nextrun := nextrun + INTERVAL ''1 Minute''; + END IF; + + -- If the result is past the end date, exit. + IF nextrun > jscend THEN + RETURN NULL; + END IF; + + -- Check to ensure that the nextrun time is actually still valid. Its + -- possible that wrapped values may have carried the nextrun onto an + -- invalid time or date. + IF ((jscminutes = ''{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}'' OR jscminutes[date_part(''MINUTE'', nextrun) + 1] = TRUE) AND + (jschours = ''{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}'' OR jschours[date_part(''HOUR'', nextrun) + 1] = TRUE) AND + (jscmonthdays = ''{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}'' OR jscmonthdays[date_part(''DAY'', nextrun)] = TRUE OR + (jscmonthdays = ''{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,t}'' AND + ((date_part(''MONTH'', nextrun) IN (1,3,5,7,8,10,12) AND date_part(''DAY'', nextrun) = 31) OR + (date_part(''MONTH'', nextrun) IN (4,6,9,11) AND date_part(''DAY'', nextrun) = 30) OR + (date_part(''MONTH'', nextrun) = 2 AND ((pgagent.pga_is_leap_year(date_part(''DAY'', nextrun)::int2) AND date_part(''DAY'', nextrun) = 29) OR date_part(''DAY'', nextrun) = 28))))) AND + (jscmonths = ''{f,f,f,f,f,f,f,f,f,f,f,f}'' OR jscmonths[date_part(''MONTH'', nextrun)] = TRUE)) THEN + + + -- Now, check to see if the nextrun time found is a) on an acceptable + -- weekday, and b) not matched by an exception. If not, set + -- runafter = nextrun and try again. + + -- Check for a wildcard weekday + gotit := FALSE; + FOR i IN 1 .. 7 LOOP + IF jscweekdays[i] = TRUE THEN + gotit := TRUE; + EXIT; + END IF; + END LOOP; + + -- OK, is the correct weekday selected, or a wildcard? + IF (jscweekdays[date_part(''DOW'', nextrun) + 1] = TRUE OR gotit = FALSE) THEN + + -- Check for exceptions + SELECT INTO d jexid FROM pgagent.pga_exception WHERE jexscid = jscid AND ((jexdate = nextrun::date AND jextime = nextrun::time) OR (jexdate = nextrun::date AND jextime IS NULL) OR (jexdate IS NULL AND jextime = nextrun::time)); + IF FOUND THEN + -- Nuts - found an exception. Increment the time and try again + runafter := nextrun + INTERVAL ''1 Minute''; + bingo := FALSE; + minutetweak := TRUE; + daytweak := FALSE; + ELSE + bingo := TRUE; + END IF; + ELSE + -- We''re on the wrong week day - increment a day and try again. + runafter := nextrun + INTERVAL ''1 Day''; + bingo := FALSE; + minutetweak := FALSE; + daytweak := TRUE; + END IF; + + ELSE + runafter := nextrun + INTERVAL ''1 Minute''; + bingo := FALSE; + minutetweak := TRUE; + daytweak := FALSE; + END IF; + + END LOOP; + + RETURN nextrun; +END; +' LANGUAGE 'plpgsql' VOLATILE; +COMMENT ON FUNCTION pgagent.pga_next_schedule(int4, timestamptz, timestamptz, _bool, _bool, _bool, _bool, _bool) IS 'Calculates the next runtime for a given schedule'; + + + +-- +-- Test code +-- +-- SELECT pgagent.pga_next_schedule( +-- 2, -- Schedule ID +-- '2005-01-01 00:00:00', -- Start date +-- '2006-10-01 00:00:00', -- End date +-- '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', -- Minutes +-- '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', -- Hours +-- '{f,f,f,f,f,f,f}', -- Weekdays +-- '{f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f,f}', -- Monthdays +-- '{f,f,f,f,f,f,f,f,f,f,f,f}' -- Months +-- ); + + + +CREATE OR REPLACE FUNCTION pgagent.pga_is_leap_year(int2) RETURNS bool AS ' +BEGIN + IF $1 % 4 != 0 THEN + RETURN FALSE; + END IF; + + IF $1 % 100 != 0 THEN + RETURN TRUE; + END IF; + + RETURN $1 % 400 = 0; +END; +' LANGUAGE 'plpgsql' IMMUTABLE; +COMMENT ON FUNCTION pgagent.pga_is_leap_year(int2) IS 'Returns TRUE is $1 is a leap year'; + + +CREATE OR REPLACE FUNCTION pgagent.pga_job_trigger() + RETURNS "trigger" AS +' +BEGIN + IF NEW.jobenabled THEN + IF NEW.jobnextrun IS NULL THEN + SELECT INTO NEW.jobnextrun + MIN(pgagent.pga_next_schedule(jscid, jscstart, jscend, jscminutes, jschours, jscweekdays, jscmonthdays, jscmonths)) + FROM pgagent.pga_schedule + WHERE jscenabled AND jscjobid=OLD.jobid; + END IF; + ELSE + NEW.jobnextrun := NULL; + END IF; + RETURN NEW; +END; +' + LANGUAGE 'plpgsql' VOLATILE; +COMMENT ON FUNCTION pgagent.pga_job_trigger() IS 'Update the job''s next run time.'; + +CREATE TRIGGER pga_job_trigger BEFORE UPDATE + ON pgagent.pga_job FOR EACH ROW + EXECUTE PROCEDURE pgagent.pga_job_trigger(); +COMMENT ON TRIGGER pga_job_trigger ON pgagent.pga_job IS 'Update the job''s next run time.'; + + +CREATE OR REPLACE FUNCTION pgagent.pga_schedule_trigger() RETURNS trigger AS ' +BEGIN + IF TG_OP = ''DELETE'' THEN + -- update pga_job from remaining schedules + -- the actual calculation of jobnextrun will be performed in the trigger + UPDATE pgagent.pga_job + SET jobnextrun = NULL + WHERE jobenabled AND jobid=OLD.jscjobid; + RETURN OLD; + ELSE + UPDATE pgagent.pga_job + SET jobnextrun = NULL + WHERE jobenabled AND jobid=NEW.jscjobid; + RETURN NEW; + END IF; +END; +' LANGUAGE 'plpgsql'; +COMMENT ON FUNCTION pgagent.pga_schedule_trigger() IS 'Update the job''s next run time whenever a schedule changes'; + + + +CREATE TRIGGER pga_schedule_trigger AFTER INSERT OR UPDATE OR DELETE + ON pgagent.pga_schedule FOR EACH ROW + EXECUTE PROCEDURE pgagent.pga_schedule_trigger(); +COMMENT ON TRIGGER pga_schedule_trigger ON pgagent.pga_schedule IS 'Update the job''s next run time whenever a schedule changes'; + + +CREATE OR REPLACE FUNCTION pgagent.pga_exception_trigger() RETURNS "trigger" AS ' +DECLARE + + jobid int4 := 0; + +BEGIN + + IF TG_OP = ''DELETE'' THEN + + SELECT INTO jobid jscjobid FROM pgagent.pga_schedule WHERE jscid = OLD.jexscid; + + -- update pga_job from remaining schedules + -- the actual calculation of jobnextrun will be performed in the trigger + UPDATE pgagent.pga_job + SET jobnextrun = NULL + WHERE jobenabled AND jobid=jobid; + RETURN OLD; + ELSE + + SELECT INTO jobid jscjobid FROM pgagent.pga_schedule WHERE jscid = NEW.jexscid; + + UPDATE pgagent.pga_job + SET jobnextrun = NULL + WHERE jobenabled AND jobid=jobid; + RETURN NEW; + END IF; +END; +' LANGUAGE 'plpgsql' VOLATILE; +COMMENT ON FUNCTION pgagent.pga_exception_trigger() IS 'Update the job''s next run time whenever an exception changes'; + + + +CREATE TRIGGER pga_exception_trigger AFTER INSERT OR UPDATE OR DELETE + ON pgagent.pga_exception FOR EACH ROW + EXECUTE PROCEDURE pgagent.pga_exception_trigger(); +COMMENT ON TRIGGER pga_exception_trigger ON pgagent.pga_exception IS 'Update the job''s next run time whenever an exception changes'; + + + +COMMIT TRANSACTION; Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/branding/branding.ini =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/branding/branding.ini (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/branding/branding.ini (revision 1448) @@ -0,0 +1,57 @@ +; +; This file (if present) controls the branding of pgAdmin. +; Each of the settings below can be used to override the +; application defaults. +; +; Lines starting with ; are comments. +; +; NOTE: All default filenames listed here are hard coded into +; the Windows installer which is not clever enough to +; parse this file. Changes here must be reflected in the +; WiX code!! + +; Application details. The shortname should be a Unix friendly +; name. The long name should be a Windows friendly long name. + +;ShortAppName=pgadmin3 +;LongAppName=pgAdmin III +;WebsiteUrl=http://www.pgadmin.org/ + +; Images +; Each of the following is an GIF format image, in the same +; directory as this file. The large icon is 32x32 and the +; small icon is 16x16. The splash image may be any reasonable +; size. Transparency is supported, and can be used to create +; funkily shaped splash/about screens. + +;LargeIcon=largeicon.gif +;SmallIcon=smallicon.gif +;SplashImage=splashimage.gif + +; The following icon is used on Windows when the task bar +; groups items together. It's also used by the installer for +; the start menu shortcut. + +;Icon=icon.ico + +; The following settings affect the text that overlays the +; splash screen. +; The font size options can be set for each platform. +; The X and Y options specify the text position. +; The Offset is the distance between the tops of each line. +; The colour option is in #nnnnnn HTML-style format. + +;SplashFontSizeGtk=9 +;SplashFontSizeMac=11 +;SplashFontSizeWin=8 + +;SplashPosX=128 +;SplashPosY=281 +;SplashPosOffset=15 + +;SplashTextColour=#FFFFFF + +; The report key colour is the main colour used in the internal +; CSS stylesheet used to format reports. + +;ReportKeyColour=#009ACE Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,29 @@ + + + + + +Guru-Hinweise + + + + +

Datenbank Kodierung

+

+Die Datenbank ist mit der Kodierung SQL_ASCII erzeugt um Daten zu speichern. Diese Kodierung ist nur für +7-Bit Zeichen definiert, was bedeutet daß die Behandlung von Zeichen mit gesetztem 8. Bit (nicht-Ascii Zeichen 127-255) nicht +festgelegt ist. In der Konsequenz ist es dem Server nicht möglich, die Daten in andere Kodierungen umzuwandeln. +

+

+Wenn nicht-Ascii Daten in der Datenbank gespeichert werden sollen, empfehlen wir dringend, eine geeignete Kodierung +zu verwenden welche dem Verwendeten Zeichensatz Rechnung trägt, um so die bedarfsweise automatische Konvertierung in verschiedene +Client-Kodierung nutzen zu können. Wenn nicht-Ascii Zeichen in einer SQL_ASCII Datenbank gespeichert werden, +kann es vorkommen daß merkwürdige Zeichen in die Datenbank geschrieben oder von ihr gelesen werden, verursacht durch +Konvertierungsprobleme. Das kann eine Menge Kopfschmerzen verursachen, insbesondere wenn auf die Datenbank mit verschiedenen +Clientprogrammen und Treibern zugegriffen wird. +

+

+Für die meisten Installationen bietet die Unicode-Kodierung (UTF8) die größte Flexibilität. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-ident.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +Guru-Hinweise + + + + +

Ident-Authentifizierung fehlgeschlagen

+

+Der Server akzeptiert den aktuellen Benutzer nicht. Der Server anwortet +

+

+ +

+

+Wenn diese Meldung erscheint, ist ein Eintrag in der pg_hba.conf-Datei gefunden worden die der +Kombination von Client-Adresse/Benutzer/Datenbank entpricht, gesetzt auf die "ident" Authentikation. +Einige Distributionen, z.B.Debian, haben dies per Default. +Um eine Ident-basierte Authentifikation erfolgreich durchzuführen, sind zusätzliche Vorkehrungen notwendig, +siehe die PostgreSQL Online-Hilfe. Für den Anfang dürfte es einfacher sein, eine andere Authentifizierungsmethode +zu verwenden. Z.B.MD5-verschlüsselte Paßworte sind eine gute Wahl, ein entsprechender Eintrag in der +pg_hba.conf sieht so aus: +

+

+host all all 192.168.0.0/24 md5 +

+

+Dieses Beispiel erlaubt MD5-verschlüsselten Paßwortzugriff auf alle Datenbanken für alle Benutzer im +privaten Netzwerksegment 192.168.0.0/24. +

+

+Zum Editieren der pg_hba.conf-Datei kann der in pgAdmin III eingebaute Editor verwendet werden. +Nach Änderungen an der Datei muß der Server über pg_ctl oder Stoppen und Starten des Serverprozesses +zum Neuauswerten der Datei veranlaßt werden. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/vacuum.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Guru-Hinweise + + + + +

VACUUM-Lauf empfohlen

+

+Die geschätzte Anzahl Zeilen in der Tabelle "" weicht erheblich von der tatsächlich ermittelten ab. +VACUUM ANALYZE sollte auf dieser Tabelle ausgeführt werden. +

+Anstatt das Kommando VACUUM ANALYZE auf dieser Tabelle manuell auszuführen (dies kann über das +Wartungs-Menü von pgAdmin III ausgelöst werden), empfiehlt es sich VACUUM ANALYZE regelmäßig +automatisiert durchzuführen. Dies kann durch einen Scheduler erreicht werden. PostgreSQL bietet auch den +pg_autovacuum Daemon, der Änderung an der Datenbank verfolgt und bei Bedarf VACUUM automatisch auslöst. +In der Regel bietet pg_autovacuum die optimale Lösung. +



+Wozu ist VACUUM überhaupt gut? +

+Der PostgreSQL Queryplaner fällt seine Entscheidung anhand von Annahmen, die er aus der geschätzten Anzahl Reihen +ableitet. Wenn die tatsächliche Anzahl zu sehr von der geschätzten Anzahl abweicht, kann der Planer eine falsche +Entscheidung treffen, wodurch ein nicht-optimaler Queryplan zur Anwendung gelangt. Daraus kann eine schlechte +Performance resultieren. +

+Die PostgreSQL Datenspeicherung benötigt VACUUM um Transaktion-IDs in Tabellen zu fixieren. +Weiterhin werden Zeilen, die nach Updates und Deletes nicht mehr benötigt werden, erst durch ein VACUUM +tatsächlich wieder freigegeben. +Weitergehende Informationen sind in der Online-Hilfe zu finden: einfach den Hilfe-Button drücken. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/instrumentation.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Guru-Hinweise + + + + +

Serverinstrumentierung

+

+Der Server hat die Instrumentierungsfunktionen nicht geladen. +

+

+pgAdmin III benutzt einige Unterstützungsfunktionen die nicht in allen PostgreSQL Versionen per Default zur Verfügung +stehen. Sie ermöglichen einige Aufgaben im Umgang mit Logdateien und Konfigurationsdateien. +

+

+Wenn PostgreSQL 8.0 oder neuer mit dem Windows Installer installiert wird, reicht es die "Admin Option" auszuwählen. +

+

+Wenn PostgreSQL aus der Source kompiliert wird, können die benötigten Dateien im xtra Unterverzeichnis des +pgAdmin Sourcetrees gefunden werden. Für PostgreSQL 8.0 ist das Verzeichnis admin unter das postgresql contrib +Sourceverzeichnis zu kopieren, make und make install führt dann die Installation durch. Für PostgreSQL 8.1 ist +das admin81 Verzeichnis zu benutzen. Nach der Installation des Modules müssen die Instrumentierungsfunktionen +in der Wartungsdatenbank erzeugt werden; hierzu dient das admin.sql Script (admin81.sql für PostgreSQL 8.1) +welches üblicherweise im pgsql share Verzeichnis zu finden ist (z.B. /usr/local/pgsql/share) +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,25 @@ + + + + + +Guru-Hinweise + + + + +

Editieren einer Tabelle ohne Primärschlüssel

+

+Da die Tabelle keien Primärschlüssel oder OID aufweist, können die Daten nur angesehen werden. +Das Einfügen von neuen Zeilen oder die Änderung existierender Zeilen mit dem Edit Data Tool ist ohne +Primärschlüssel nicht möglich. +

+

+Um Daten editieren zu können, erfordert pgAdmin III einen Primärschlüssel auf der Tabelle, was i.d.R. ohnehin +im Rahmen eines guten Datenbankdesigns vorhanden sein sollte. +Alternativ kan die Tabelle auch WITH OIDS angelegt werden. Bitte beachten daß Eindeutigkeit von OIDs nicht +über sehr lange Zeiträume gewährleistet werden kann, so daß die Verwendung von Oids nur als zweite Wahl im Vergleich +zu einem Primärschlüssel anzusehen sind. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-hba.html (revision 1448) @@ -0,0 +1,42 @@ + + + + + +Guru-Hinweise + + + + +

Zugriff auf die Datenbank verweigert

+

+Der Server erlaubt keinen Zugriff auf die Datenbank. Der Server meldet +

+

+ +

+

+Um eine Datenbank auf einem PostgreSQL-Server ansprechen zu können, mußt zuerst die grundätzliche +Zugangsfreigabe für den Client erteilt werden (Host Based Authentication). PostgreSQL prüft die pg_hba.conf-Datei +ob ein Muster welches der Client-Adresse/Benutzername/Datenbank entspricht vorhanden und aktiviert +ist noch bevor eventuelle SQL GRANT Zugriffsbeschränkungen zum Tragen kommen. +

+

+Die anfänglichen Einstellungen in der pg_hba.conf sind recht restriktiv, um unerwünschten Sicherheitslöcher +vorzubeugen, wenn diese Datei nicht editiert wird. Typischerweise werden Zugriffsregeln der folgenden Form +erforderlich werden: +

+

+host all all 192.168.0.0/24 md5 +

+

+Dieses Beispiel erlaubt MD5-verschlüsselten Paßwortzugriff auf alle Datenbanken für alle Benutzer im +privaten Netzwerksegment 192.168.0.0/24. +

+

+Zum Editieren der pg_hba.conf-Datei kann der in pgAdmin III eingebaute Editor verwendet werden. +Nach Änderungen an der Datei muß der Server über pg_ctl oder Stoppen und Starten des Serverprozesses +zum Neuauswerten der Datei veranlaßt werden. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/autovacuum.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Guru-Hinweise + + + + +

Aktivierung von pg_autovacuum empfohlen

+

+Seit PostgreSQL 8.1 ist der pg_autovacuum-Prozess, der vormals als externer Dienst +implementiert war, in das Backend integriert worden. Er führt VACUUM automatisch +aus, wenn sich die Daten in einem konfigurierbaren Umfang geändert haben. +

+

+Das Laufenlassen von VACUUM ist erforderlich für einen PostgreSQL Server, +um die Daten konsistent zu halten und die Performance zu erhalten. +Zum Einstieg empfiehlt es sich, pg_autovacuum einzuschalten, indem die Einstellungen +'autovacuum', 'stats_start_collector' and 'stats_row_level' in der postgresql.conf +auf 'on' gesetzt werden. Die damit einhergehende Performanceeinbuße ist normalerweise +nicht spürbar, man gewinnt jedoch die Sicherheit der automatisierten VACUUM-Läufe. +

+

+Um die pg_autovacuum Performance für individuelle Anforderungen anzupassen, +kann es erforderlich werden die globalen Einstellungen in postgresql.conf oder +für einzelne Tabellen anzupassen; siehe hierzu die Dokumentation. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/conn-listen.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Guru-Hinweise + + + + +

Der Server antwortet nicht

+

+Der Server akzeptiert keine Verbindungen: Die Verbindungslibrary berichtet +

+

+ +

+

+Wenn diese Meldung auftaucht, sollte geprüft werden ob der PostgreSQL-Server tatächlich auf dem angegebenen +Port läuft. Ist Netzwerk-Connectivity von der Client-Maschine zur Servermaschine gegeben? Sind Netzwerk/VPN/SSH-Tunnel +korrekt konfiguriert? +

+

+Aus Sicherheitsgründen reagiert PostgreSQL anfänglich nicht auf allen verfügbaren IP-Adressen der Servermaschine. Um den Server +über das Netzwerk ansprechen zu können, müssen die Interfaces erst aktiviert werden. +

+

+Für PostgreSQL-Server ab Version 8.0 wird dies durch den "listen_addresses"-Parameter in the postgresql.conf-Datei gesteuert. Hier +wird die Liste aller zu bedienenden IP-Adressen eingetragen, oder einfach '*' um alle verfügbaren Interfaces zu bedienen. Für ältere Versionen +(Version 7.3 oder 7.4), ist der Parameter "tcpip_socket" auf 'true' zu setzen. +

+

+Zum Editieren der postgresql.conf-Datei kann der in pgAdmin III eingebaute Editor verwendet werden. +Nach Änderungen an der Datei muß der Server neu gestartet werden um die Änderungen aktiv zu machen. +

+

+Wenn nach doppelter Prüfung der Konfiguration diese Fehlermeldung immer noch kommt, ist +es trotzdem sehr unwahrscheinlich daß tatsächlich ein Fehlverhalten des PostgreSQL-Servers vorliegt. +Vermutlich gibt es ein grundlegendes Netzwerkproblem (z.B. Firewall-Konfiguration). Dies sollte eingehend geprüft +werden, bevor ein vermeintlicher Bug an die PostgreSQL Community gemeldet wird. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/fki.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Guru-Hinweise + + + +

Fremdschlüssel abdeckende Indizes

+

+Ein Fremdschlüssel koppelt zwei Tabellen auf logische Weise, und beschränkt Änderungen die auf sie angewendet werden können. +

+

+Es fängt mit einer Mastertabelle an, welche die Referenzierte Tabelle wird. Sie muß einen Primärschlüssel haben +(strenggenommen müssen die referenzierten Spalten nur nicht-NULL sein und mit einem eindeutigen Index versehen sein, +aber es ist gute Praxis das über einen Primärschlüssel zu implementieren). Die Slave-Tabelle hängt von der Mastertabelle ab, +in dem Sinne daß Spalten auf die der Fremdschlüssel definiert ist für jeden Wert passende Einträge in der Mastertabelle erfordert. +Die Slave-Tabelle ist die referenzierende Tabelle des Fremdschlüssels. +

+

+Der Fremdschlüssel beschränkt allerdings nicht nur die referenzierende Tabelle, sondern auch die referenzierte. Die +Geschmacksrichtung kann dabei zwischen RESTRICT, CASCADE und SET NULL variieren. Dies bedeuted, daß sobale +eine Zeile in der referenzierten Tabelle geändert wird (Update oder Delete), alle referenzierenden Tabelen geprüft werden müssen +ob die Operation gültig ist, und ob weitere Aktionen ausgelöst werden müssen; siehe hierzu auch die PostgreSQL-Dokumentation +über Fremdschlüssel (Foreign Keys). +

+

+Dies bedeutet, daß Änderungen an einer bestimmten Zeile in der referenzierten Tabelle zusätzliche Lesezugriffe +in allen referenzierenden Tabellen auslöst, mit den Fremdschlüssel als Zugriffsbegriff. In der Konsequenz sollten alle Designregeln +für performanten Lesezugriff auch auf die Fremdschlüsselspalten angewendet werden. Für gute Zugriffsgeschwindigkeiten +ist in der Regel ein Index empfehlenswert. PostgreSQL verlangt dies nicht unbedingt, es liegt daher in der Verantwortung +des Datenbankdesigners für das Anlegen eines passenden Index zu sorgen. +

+

+Zur Steigerung des Komforts und des allgemeinen Wohlbefindens bietet pgAdmin III eine Checkbox an, mit deren Hilfe +auf einen passenden Index geprüft wird und dieser bei Bedarf angelegt wird soweit noch nicht vorhanden. Wie bei allen Indizes gibt +es Fälle in denen Indizes die Gesamtperformance verringern können; in aller Regel ist ein Index zu wenig jedoch wesentlich +schlimmer als einer zuviel. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,26 @@ + + + + + +Guru-Hinweise + + + + +

Unicode-Kodierung auf einem Win32 Server

+

+Die Datenbank ist in Unicode-Kodierung (UTF8) angelegt +und wird mit PostgreSQL 8.0 auf einem Windows-Server (Win32) betrieben. +

+

+Die PostgreSQL 8.0 Win32 Implementierung kann Unicode-Zeichenketten nicht anhand der korrekten +Collation Sequence sortieren, da das Betriebssystem diese Funktion nicht bietet. +

+

+Es wird empfohlen, eine lokal spezifische Kodierung zu verwenden oder den Cluster auf +einem anderen Betriebssystem als Win32 laufen zu lassen. Alternativ können Sie die Datenbanksoftware auf PostgreSQL 8.1 (oder neuer) +aktualisieren, das diese Einschränkung von Win32 umgehen kann. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/pk.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Guru-Hinweise + + + + +

Primärschlüssel

+

+Beim Designen einer Tabelle sollte man stehts im Blick behalten, auf welche Weise später auf sie +zugegriffen wird. In den meisten Fällen wird ein eindeutiger Schlüsselbegriff erforderlich sein um eine +spezifische Zeile jeweils eindeutig identifizieren zu können. Dieser Schlüsselbegriff sollte als Primärschlüssel +erzeugt werden. +Ein Primärschlüssel muß nicht unbedingt aus einer einzelnen Spalte bestehen; er kann soviel Spalten beinhalten wie nötig +um eine Zeile eindeutig zu identifizieren. Wenn hierzu allerdings viele Spalten erforderlich sein sollten (Faustregel: mehr als 3) +könnte es eine gute Idee sein eine zusätzliche Spalte mit einem handlichen Datentyp, z.b. serial oder bigserial, einzuführen, +welche den eindeutigen Schlüssel enthält. +

+

+Nur in seltenen Ausnahmefällen macht das Erzeugen eines Primärschlüssels keinen Sinn. Das bedeutet, daß das Fehlen eines +Primärschlüssels in einer Tabelle auf eine unvollständige Definition hinweist; darum kommt der Guruhinweis hoch +wenn man eine Tabelle ohne PK anzulegen versucht. +

+

+Wenn man einen Blick auf die PostgreSQL-Systemtabellen wirft, stellt man fest daß keine von ihnen einen Primärschlüssel aufweist, +also was soll das Ganze? Tatsächlich haben alle diese Tabellen eine oder zwei Spalten (typischerweise nur die OID), welche +jede Zeile eindeutig identifiziert, welche die zweite Regel für einen Primärschlüssel, nicht NULL enthalten zu dürfen, befolgt, und einen +Index für schnelleren Zugriff beinhaltet. Die Verwendung von OIDs hat historische Gründe, und ist nicht gerade erste Wahl wenn es um den Design +von User-Tabellen geht. PostgreSQL benutzt diese um Rückwärtskompatibilität zu gewährleisten. Aus heutiger Sicht würde man vermutlich +Primärschlüssel verwenden, eine dahingehende Änderung der Systemtabellen ist allerdings nicht zu erwarten. +

+

+Wie das Beispiel der Systemtabellen zeigt, kann das Ziel der Eindeutigkeit und des schnellen Zugriffs auch auf andere Weise +als mit einem Primärschlüssel erreicht werden. Es ist allerdings sehr empfehlenswert, aus Gründen der Klarheit des Datenmodells +stets Primärschlüssel zu verwenden. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Guru-Hinweise + + +

+pgAdmin III hat mehrere Hinweise zum aktuellen Objekt. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/de_DE/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +PostgreSQLs Performance kann durch regelmÀßige VACUUM-LÀufe verbessert werden. +PostgreSQLs offizieller Geburtstag ist der 8. Juli. Das PostgreSQL-Projekt wurde 1996 geboren. +Der erste Prototyp fÃŒr das ursprÃŒngliche pgAdmin-Projekt nannte sich pgManager und war fÃŒr PostgreSQL 6.3.2 geschrieben. +Support fÃŒr pgAdmin kann durch die Mailingliste pgadmin-support@postgresql.org angefordert werden. +Die pgAdmin-Entwickler diskutieren neue Features und Entwicklungen auf der Mailingliste pgadmin-hackers@postgresql.org. +Das Meiste der pgSchema-Bibliothek, die durch pgAdmin II verwendet wurde, wurde auf einem Windows-2000-Laptop vor einem Fernseher in der NÀhe von Oxford, England entwickelt! +Das Passwort kann durch "Passwort Àndern.." im "Datei"-MenÃŒ geÀndert werden. +Die DefinitionflÀche zeigt das zurÃŒckÃŒbersetzte SQL-Script fÃŒr das gewÀhlte Objekt an. +Die Antwort auf die Frage nach dem Sinn des Lebens, des Universums und dem ganzen Rest ist 42. +Die pgAdmin Core-Entwickler sind in Großbritannien, Frankreich, Deutschland, Italien und den USA zu Hause. +PostgreSQL Version 7.2 und spÀtere unterstÃŒtzen Tabellen ohne OID-Spalten, um den Verbrauch von OIDs zu senken. +Die SystemaktivitÀt eines Servers kann mit dem Statustool verfolgt werden. +Einige zusÀtzliche interessante Dateien, Tools und Projekte sind im Quellbaum von PostgreSQL im /contrib-Verzeichnis enthalten. +PostgreSQLs prozedurale Sprachen sind u.a. PL/pgSQL, PL/Python, PL/TCL, PL/Perl und PL/sh. +pgAdmin II wurde mehr als 10.000 mal heruntergeladen *bevor* das erste stabile Release freigegeben war! +Die erste stabile Version von pgAdmin II wurde ÃŒber 35.000 mal in den ersten 6 Monaten nach dem Release heruntergeladen. +Das Slony-I Projekt von www.slony.info kann fÃŒr Master->Slave Replikationen verwendet werden. +Die erste offizielle stabile Version von pgAdmin II wurde am 16.01.2002 freigegeben. +Die Entwicklung von pgAdmin III startete am 29.09.2002. +pgAdmin III ist eine komplett neu in C++ geschriebene Version von pgAdmin unter Verwendung des wxWidgets Frameworks, um zahlreiche Plattformen wie Windows und *nix-Systeme zu unterstÃŒtzen. +pgAdmin ist unter der Open Source 'Artistic Licence' freigegeben. +PostgreSQL 7.3 unterstÃŒtzt Schemas die individuelle NamensrÀume innerhalb einer Datenbank darstellen. +DomÀnen können benutzt werden, um spezialisierte Datentypen, die auf Standarddatentypen basieren, zu definieren. +pgAdmin III 1.0.0 wurde am 26. September 2003 freigegeben. +PostgreSQLs Query Planner kann keine Indexscans verwenden, wenn die verbindenden Spalten unterschiedliche Datentypen haben. +Mann sollte niemals den Postmaster mit 'kill -9' abschießen!! +'EXPLAIN ANALYZE' und der 'Abfrage zerlegen' Knopf sind Freunde beim Optimieren von SQL-Queries. +PostgreSQL 8.0 fÃŒgte umfangreiche neue Features zum DBMS hinzu, zum Beispiel Savepoints, Tablespaces und die sehnsÃŒchtig erwartete native Windows-Version. +pgAdmin III unterstÃŒtzt SSL-verschlÃŒsselte Verbindungen. +Der neue Windows-Port von PostgreSQL absolvierte alle Regressionstest erstmalig am 24.10.2004. +Die Windows-Version von PostgreSQL 8.0 wurde ÃŒber 45.000 mal in den ersten fÃŒnf Tagen nach Ertfreigabe heruntergeladen! +Der Bug "Don't enable the OK button when setting the ACL for as-yet-uncreated objects" wurde in 39.000 Fuß Höhe ÃŒber Finnland gefixt wÀhrend Andreas, Magnus and Dave vom Slony-I and pgAdmin III Seminar in Japan zurÃŒckkehrten! +PostgreSQL mit zuvielen Shared Buffers zu konfigurieren kann sich nachteilig auf die Performance auswirken, weil es den Speicherplatz fÃŒr den Dateisystemcache des Betriebssystems verringert. +12 Stunden lang in einem Flugzeug zu sitzen ist nervtötend langweilig, deswegen schreibe ich ein paar neue Tips! +Die Japan PostgreSQL Users Group oder auch JPUG hat ÃŒber 5000 Mitglieder und wÀchst weiter. +pgAdmin 1.4 unterstÃŒtzt mehr Plattformen als jede vorhergehende Version, inklusive zahlreicher Linux-Distributionen, Microsoft Windows (tm), FreeBSD, Solaris und Mac OS X. +pgAdmin 1.4 enthÀlt ein grafisches EXPLAIN-Werkzeug, welches die Auswertung von QueryplÀnen erleichtert. +pgAgent kann benutzt werden, um regelmÀßig anfallende Batch- und SQL-Jobs auszufÃŒhren, z.B. Neuerzeugung datumsabhÀngiger partieller Indizes, oder um alte Daten aufzurÀumen. +Es ist eine gute Gewohnheit, Teile der Applikationslogik in die Datenbank selber mit Hilfe von Funktionen und Views einzubauen. Dadurch wird sichergestellt, damit verschiedene Frontends immer die gleiche Sicht auf die Daten haben und die Daten auf gleichartige Weise verÀndern. Und nicht zuletzt muss die Logik nur einmal geschrieben werden! +Um die Datenbank sicher zu halten, sollte der Zugang fÃŒr entfernte Rechner in der Konfigurationsdatei pg_hba.conf auf das Minimum beschrÀnkt werden und stets eine verschlÃŒsselte Verbindung verwendet werden, wenn es nicht sehr gute GrÃŒnde gibt, die dagegen sprechen. +Der Zugriff auf einzelne Spalten einer Tabelle fÃŒr bestimmte Benutzer oder Gruppen kann eingeschrÀnkt werden, indem der direkte Zugriff auf die Tabelle unterbunden wird und stattdessen ein View, der nur die zugÀnglichen Spalten enthÀlt, definiert wird. Wenn der Benutzer die Daten Àndern soll, kann dies durch Regeln auf dem View erledigt werden, die bei Änderungen die dahinterliegende Tabelle ansprechen. +PostgreSQL lÀuft auch auf fÃŒr Datenbanksysteme eher exotischen Plattformen wie Microsoft X Box, Sony PlayStation II, und Sharp Zaurus PDAs! +EnterpriseDB sponsorte dem pgAdmin-Projekt ein Apple Powerbook, um die Mac OS X-Portierung von pgAdmin und dem davon abgeleiteten vereinfachten Produkt, EDB Studio, zu unterstÃŒtzen. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

ÊýŸÝ¿â±àÂë

+

Êý ŸÝ ¿â ʹ Óà SQL_ASCII ±à Âë Ž¢ Žæ Êý ŸÝ£¬ Õâ žö ±à Âë ±» ¶š Òå Ϊ œö ÓÐ 7žö λ µÄ ×Ö ·û£¬ +Òâ ζ ׊ʹ Óà µÚ 8žö λ µÄ ×Ö ·û £š·Ç ASCII ×Ö ·û 127-255£© ÎÞ ·š ¶š Òå¡£ +Òò ŽË£¬ °Ñ ·þ Îñ Æ÷ Êý ŸÝ ת »» Ϊ Æä Ëû ±à Âë ÊÇ ²» ¿É ÄÜ µÄ¡£

+

Èç ¹û Ïë ÔÚ Êý ŸÝ ¿â ÖÐ Ž¢ Žæ ·Ç ASCII Êý ŸÝ£¬ Ñ¡ Óà һ žö Ç¿ Žó µÄ Êý ŸÝ ¿â ±à Âë ÀŽ ±í ÊŸ ±Ÿ µØ »¯ ×Ö ·û Œ¯£¬ +Ëü ÓŠ žÃ ÄÜ ¹» Ö§ ³Ö ×Ô ¶¯ ת »» Éõ ÖÁ µ± Ðè Òª µÄ ʱ ºò ¿É ÒÔ Ê¹ Óà ²» ͬ ¿Í »§ ¶Ë ±à Âë¡£ +ÔÚ SQL_ASCII Êý ŸÝ ¿â ÖÐ Ž¢ Žæ ·Ç ASCII Êý ŸÝ£¬ ¿É ÄÜ »á Òò Ϊ ±à Âë ת »» ÎÊ Ìâ ¶ø Óö µœ ŽÓ Êý ŸÝ ¿â ÖÐ ¶Á ÐŽ Êý ŸÝ ʱ ³ö ÏÖ Ææ ¹Ö ×Ö ·û µÄ ÎÊ Ìâ¡£ +µ± ʹ Óà ²» ͬ ¿Í »§ ¶Ë ºÍ Çý ¶¯ ³Ì Ðò ·Ã ÎÊ Êý ŸÝ ¿â ʱ£¬ Õâ œ« Áî ÈË ·Ç ³£ Í· ÌÛ¡£

+

+¶Ô Žó ¶à Êý °² ×° ¶ø ÑÔ£¬ Unicode £šUTF8£© ±à Âë Ìá ¹© ÁË ×î Áé »î µÄ Œæ ÈÝ ÄÜ ÁŠ¡£

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-ident.html (revision 1448) @@ -0,0 +1,34 @@ + + + + + +Guru Hints + + + + +

IdentÈÏրʧ°Ü

+

+·þ Îñ Æ÷ ÎÞ ·š œÓ ÊÜ µ± Ç° µÄ Óà »§£º ·þ Îñ Æ÷ ±š žæ +

+

+ +

+

+Èç ¹û ³ö ÏÖ Õâ žö Ïû Ï¢£¬ ˵ Ã÷ Äã µÄ ¿Í»§¶Ë / Óû§ / ÊýŸÝ¿â ×é ºÏ ÔÚ pg_hba.conf ÖÐ ±» Éè Öà Ϊ "ident" ÈÏ Ö€¡£ +ÔÚ Ò» Щ ·¢ ²Œ µ± ÖУ¬ ±È Èç Debian£¬ Õâ ÊÇ È± Ê¡ Éè Öá£ Ϊ ÁË ÄÜ ¹» ³É ¹Š ÖŽ ÐÐ »ù ÓÚ ident µÄ ÈÏ Ö€£¬ Ðè Òª œø ÐÐ ¶î Íâ µÄ Éè Öà £¬ Çë ²é ¿ŽPostgreSQL °ï Öú¡£ +¶Ô ³õ ѧ Õß ÀŽ ˵£¬ ʹ Óà Æä Ëü µÄ ÈÏ Ö€ ·œ Êœ ¿É ÄÜ žü ºÏ ÊÊ£¬ Óà MD5 ŒÓ ÃÜ ÃÜ Âë ÊÇ žö ºÃ Ö÷ Ò⣬ ¿É ÒÔ ÔÚ pg_hba.conf Õâ Ñù Åä Ö㺠+

+

+host all all 192.168.0.0/24 md5 +

+

+Õâ žö Àý ×Ó ÔÊ Ðí Ëœ ÓÐ Íø Âç 192.168.0.0/24 ʹ Óà MD5 ŒÓ ÃÜ µÄ ÃÜ Âë Á¬ œÓ µœ Ëù ÓÐ Óà »§ ºÍ Ëù ÓÐ Êý ŸÝ ¿â¡£ +

+

+Àû Óà Õû ºÏ œø pgAdmin III µÄ pg_hba.conf ±à Œ­ Æ÷ ¿É ÒÔ ÐÞ žÄ pg_hba.conf Åä Öà ÎÄ Œþ£¬ +ÐÞ žÄ Íê ±Ï ÒÔ ºó£¬ Ðè Òª ʹ Óà pg_ctl Íš Öª Êý ŸÝ ¿â ÖØ Ð ¶Á Èë Åä Öà »ò Õß ÖØ Ð Æô ¶¯ Êý ŸÝ ¿â¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/vacuum.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Guru Hints + + + + +

ÍÆŒöÔËÐÐVACUUM

+

+"" ÖÐ µÄ Ô€ ²â ÐÐ Êý ÒÑ Ÿ­ ÑÏ ÖØ Æ« Àë ʵ ŒÊ ÐÐ Êý£¬ ÓŠ žÃ ÔÚ Õâ žö Êý ŸÝ ±í ÉÏ ÔË ÐÐ VACUUM ANALYZE¡£ +

+³ý È¥ ÊÖ ¶¯ ÔË ÐÐ VACUUM ANALYZE Ãü Áî £š Ò² ¿É ÒÔ Àû Óà pgAdmin III µÄ ¡°Î¬ »€¡± ²Ë µ¥ ÀŽ ×ö £© Ö® Í⣬ +»¹ ÓŠ žÃ ¿Œ ÂÇ ¶š ÆÚ ÓÐ ¹æ ÂÉ »ò Õß ×Ô ¶¯ µØ ÔË ÐÐ VACUUM ANALYZE¡£Ê¹ Óà µ÷ ¶È ³Ì Ðò ¿É ÒÔ ×ö µœ Õâ Ò» µã£¬ +Áí Íâ PostgreSQL Ò² Ìá ¹© ÁË Ò» žö œÐ ×ö pg_autovacuum µÄ ºó Ìš ³Ì Ðò£¬ +ÄÜ ¹» žú ×Ù Êý ŸÝ ¿â µÄ ±ä »¯ ²¢ ÔÚ ÊÊ µ± ʱ ¿Ì ×Ô ¶¯ µ÷ Óà vacuum Ãü Áî¡£ +ÔÚ Žó ¶à Êý Çé ¿ö Ï£¬ pg_autovacuum ÊÇ ×î ºÃ µÄ Ñ¡ Ôñ¡£ +



+VACUUMÓÐʲκΊ£¿ +

+PostgreSQL µÄ ²é ѯ ŒÆ »® žù ŸÝ Ô€ ²â ÐÐ Êý ×ö ³ö Ÿö ¶š£¬ Èç ¹û ʵ ŒÊ ÐÐ Êý Óë Ô€ ²â ÐÐ Êý ÓÐ Ì« Žó ²î Ò죬 +¿É ÄÜ »á ×÷ ³ö Ží Îó ÅÐ ¶Ï£¬ Ôì ³É ²é ѯ ŒÆ »® ²» ÊÇ ×î ÓÅ »¯ µÄ £¬ µŒ Ö ֎ ÐРЧ ÂÊ ¹ý µÍ ¡£ +

+PostgreSQL Êý ŸÝ ¿â Ðè Òª VACUUM ÐÞ žŽ ±í ÖÐ µÄ Ê Îñ ID¡£ +Áí Í⣬ ÓÉ ÓÚ žü РºÍ ÉŸ ³ý ²Ù ×÷ ¶ø ²ú Éú µÄ ¹ý ʱ Êý ŸÝ Ö± µœ ÔÚ Õâ žö ±í ÉÏ ÔË ÐÐ VACUUM Ãü Áî ²Å »á ±» Çå Àí¡£ +°Ž Ï °ï Öú °Ž Å¥£¬ ¿É ÒÔ ŽÓ ÔÚ Ïß ÎÄ µµ ÖÐ ¿Ž µœ žü Ïê Ïž ЊϢ¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/instrumentation.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru Hints + + + + +

·þÎñÆ÷ÖžÁî

+

+·þ Îñ Æ÷ ȱ ·Š Öž Áî º¯ Êý¡£ +

+

+pgAdmin III ʹ Óà µÄ Ò» Щ Ö§ ³Ö º¯ Êý ²» ÊÇ ÔÚ Ëù ÓÐ PostgreSQL °æ ±Ÿ ÉÏ È± Ê¡ ÓРЧ£¬ +Õâ Щ º¯ Êý ʹ Ò» Щ Öî Èç ŽŠ Àí ÈÕ ÖŸ ÎÄ Œþ ºÍ Åä Öà ÎÄ Œþ µÄ ¹€ ×÷ ±ä µÃ žü ŒÓ Œò µ¥¡£ +

+

+µ± ʹ Óà Windows °² ×° ³Ì Ðò °² ×° PostgreSQL 8.0 »ò Õß žü žß °æ ±Ÿ ʱ£¬ œö œö Ðè Òª Ñ¡ ÖÐ ¡°admin¡± »ò Õß ¡°dminpack¡± Ä£ ¿é¡£ +

+

+µ± ŽÓ ÔŽ Žú Âë ÖÐ ±à Òë ʱ£¬ ±Ø Òª µÄ ÎÄ Œþ ¿É ÒÔ ÔÚ ÔŽ Žú Âë Ê÷ µÄ xtra ×Ó Ä¿ ÂŒ ÖÐ ÕÒ µœ¡£ +¶Ô ÓÚ PostgreSQL 8.0£¬ œ« admin Ä¿ ÂŒ ¿œ ±Ž µœ postgresql ÔŽ Žú Âë µÄ contrib Ä¿ ÂŒ ÖУ¬ ŽÓ Õâ Àï ±à Òë ºÍ °² ×° Ëü¡£ +¶Ô ÓÚ PostgreSQL 8.1£¬ ʹ Óà admin81 Ä¿ ÂŒ¡£ +

+PostgreSQL 8.2 ÒÔ Œ° žü žß °æ ±Ÿ ÔÚ ¡°adminpack¡± Ä£ ¿é ÖÐ °ü º¬ Öž Áî º¯ Êý¡£ +

+

+ÔÚ Ä£ ¿é °² ×° Ö® ºó£¬ ±Ø Ðë ʹ Óà admin.sql œÅ ±Ÿ £š¶Ô ÓÚ PostgreSQL 8.1 ÊÇ admin81.sql£© ÔÚ Ëù Òª ά »€ µÄ Êý ŸÝ ¿â ÖÐ ŽŽ œš Öž Áî º¯ Êý£¬ +Õâ Щ œÅ ±Ÿ ÎÄ Œþ Íš ³£ ¿É ÒÔ ÔÚ pgsql µÄ ¹² Ïí Ä¿ ÂŒ £šÀý Èç /usr/local/pgsql/share£© ÖÐ ÕÒ µœ¡£ +

+

+À© Õ¹ ·þ Îñ Æ÷ Öž Áî ÔÚ PostgreSQL 7.3 ºÍ 7.4 ÖРû ÓÐ ±» Ö§ ³Ö¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

±àŒ­Ã»ÓÐÖ÷ŒüµÄ±íÊýŸÝ

+

+±í û ÓÐ Ö÷ Œü »ò Õß OID ×Ö ¶Î£¬Ö» ÄÜ ²é ¿Ž Êý ŸÝ¡£ +ÔÚ Ã» ÓÐ Ö÷ Œü µÄ Çé ¿ö Ï ²» ÄÜ Ê¹ Óà Êý ŸÝ ±à Œ­ ¹€ Ÿß ²å Èë РÊý ŸÝ ÐÐ ºÍ ÐÞ žÄ ÒÑ Ÿ­ Žæ ÔÚ µÄ Êý ŸÝ¡£ +

+

+Ϊ ÁË ±à Œ­ Êý ŸÝ£¬pgAdmin III Òª Çó Êý ŸÝ ±í Ÿß ÓÐ Ö÷ Œü£¬Õâ Ò² ÊÇ Ò» žö ºÃ µÄ Êý ŸÝ ¿â Éè ŒÆ Ï° ¹ß¡£ +Áí Íâ »¹ ÓÐ Ò» ÖÖ Ìæ Žú ·œ Êœ£º ʹ Óà OID ×Ö ¶Î ŽŽ œš Êý ŸÝ ±í¡£ Çë ×¢ Òâ OID ÔÚ Ÿ­ ¹ý ºÜ ³€ Ò» ¶Î ʱ Œä Ö® ºó ²» ÄÜ ±£ Ö€ »¹ ÊÇ Îš Ò» µÄ¡£ +Òò ŽË ʹ Óà OID ×÷ Ϊ Ö÷ Œü œö œö ÊÇ µÚ ¶þ Ñ¡ Ôñ¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-hba.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru Hints + + + + +

·ÃÎÊÊýŸÝ¿â±»ŸÜŸø

+

+·þ Îñ Æ÷ ²» ÔÊ Ðí ·Ã ÎÊ Êý ŸÝ ¿â£º ·þ Îñ Æ÷ ±š žæ +

+

+ +

+

+·Ã ÎÊ PostgreSQL Êý ŸÝ ¿â£¬ Ê× ÏÈ ±Ø Ðë ÔÊ Ðí ¿Í »§ ¶Ë ÄÜ ¹» Á¬ œÓ Ö÷ »ú £š»ù ÓÚ Ö÷ »ú µÄ ÈÏ Ö€£©£¬ +È» ºó ÔÚ Ëù ÓÐ SQL ·Ã ÎÊ Èš ÏÞ ±» Ñé Ö€ Ö® Ç°£¬ PostgreSQL œ« Œì ²é pg_hba.conf ÎÄ Œþ ²é ¿Ž ÊÇ ·ñ ÓÐ Óë ¿Í »§ ¶Ë µÄ µØÖ· / Óû§Ãû / ÊýŸÝ¿â Ïà ·û ºÏ µÄ ·œ °ž Žæ ÔÚ ²¢ ÇÒ ÊÇ ÔÊ Ðí ·Ã ÎÊ µÄ¡£ +

+

+ΪÁ˱ÜÃâÓÉϵͳÒýÆðµÄ²»±ØÒªµÄ°²È«Â©¶Ž£¬pg_hba.confÖеijõÊŒÉèÖÃÊ®·ÖÑÏžñ£¬¿ÉÒÔÏñÏÂÃæÕâÑùÔöŒÓÉèÖ㺠+

+

+host all all 192.168.0.0/24 md5 +host all all 192.168.0.0/24 md5 +

+

+Õâ žö Àý ×Ó ÔÊ Ðí Ëœ ÓÐ Íø Âç 192.168.0.0/24 ʹ Óà MD5 ŒÓ ÃÜ µÄ ÃÜ Âë Á¬ œÓ µœ Ëù ÓÐ Óà »§ ºÍ Ëù ÓÐ Êý ŸÝ ¿â¡£ +

+

+Àû Óà Õû ºÏ œø pgAdmin III µÄ pg_hba.conf ±à Œ­ Æ÷ ¿É ÒÔ ÐÞ žÄ pg_hba.conf Åä Öà ÎÄ Œþ£¬ +ÐÞ žÄ Íê ±Ï ÒÔ ºó£¬ Ðè Òª ʹ Óà pg_ctl Íš Öª Êý ŸÝ ¿â ÖØ Ð ¶Á Èë Åä Öà »ò Õß ÖØ Ð Æô ¶¯ Êý ŸÝ ¿â¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/object-editing.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/object-editing.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/object-editing.html (revision 1448) @@ -0,0 +1,32 @@ + + + + + +Guru Hints + + + + +

±àŒ­ÊÓÍŒ¡¢ŽæŽ¢¹ý³Ì»òÕߺ¯Êý

+

+µ± ±à Œ­ ÊÓ ÍŒ¡¢ Žæ Ž¢ ¹ý ³Ì »ò Õß º¯ Êý µÄ Žú Âë ʱ£¬ ²» ʹ Óà λ ÓÚ ¶Ô Ïó Êô ÐÔ ¶Ô »° ¿ò ÉÏ µÄ С ÎÄ ±Ÿ ¿ò£¬ ¶ø ÊÇ Ê¹ Óà pgAdmin µÄ œÅ ±Ÿ Ñ¡ Ïî ÔÚ ²é ѯ ¹€ Ÿß ÖÐ ±à Œ­ Ëü¡£ ²é ѯ ¹€ Ÿß µÄ ±à Œ­ Æ÷ Ÿß ÓÐ ×Ô ¶¯ Íê ³É¡¢ ²é ÕÒ Ìæ Žú ¹Š ÄÜ ÒÔ Œ° žü Žó µÄ ¹€ ×÷ ¿Õ Œä£¬ Õâ Ñù ¿É ÄÜ »á žü ŒÓ ·œ ±ã¡£

+ +

+¿É ÒÔ Íš ¹ý ÔÚ pgAdmin µÄ ä¯ ÀÀ Ž° ¿Ú Ï£ Íû ±à Œ­ µÄ ¶Ô Ïó ÉÏ µã »÷ ÓÒ Œü£¬ +È» ºó Ñ¡ Ôñ ¡°ŽŽ œš œÅ ±Ÿ¡± ²Ë µ¥£¬ ÀŽ ʹ Óà œÅ ±Ÿ Ñ¡ Ïî¡£ ÓРʱ ¿É ÄÜ ³ö ÏÖ ¡°œÅ ±Ÿ¡± ×Ó ²Ë µ¥£¬ +ÄÇ ÃŽ Õâ ʱ ºò ¿É ÒÔ Ñ¡ ÖÐ ¶Ô Ïó£¬ È» ºó ÔÚ ¡°¹€ Ÿß¡± ²Ë µ¥ µÄ ¡°œÅ ±Ÿ¡± ×Ó ²Ë µ¥ ÖÐ Ñ¡ Ôñ ¡°ŽŽ œš œÅ ±Ÿ¡±¡£

+ +

+±à Œ­ ¶Ô Ïó Ðè Òª ±ä žü µÄ ¶š Ò壬 È» ºó ʹ Óà ¡°ÖŽ ÐÐ ²é ѯ¡± °Ž Å¥ Ìá œ»¡£ +²» Òª Íü ŒÇ£¬ ÐÞ žÄ ÊÓ ÍŒ »ò º¯ Êý µÄ Ãû ×Ö £¬ »ò Õß ÐÞ žÄ º¯ Êý »ò Žæ Ž¢ ¹ý ³Ì µÄ Ç© Ãû £¬ +»á ÔÚ Ô­ ÏÈ ¶Ô Ïó µÄ ÅÔ ±ß œš Á¢ Ò» žö Р¶Ô Ïó£¬ Õâ ¶Ô ÓÚ œš Á¢ Ò» žö РµÄ Ïà ËÆ ¶Ô Ïó œ« ÊÇ Ê® ·Ö ·œ ±ã µÄ ¡£ È» ºó Ðè Òª Ë¢ РpgAdmin ä¯ ÀÀ Æ÷ ÏÔ ÊŸ Рœš ¶Ô Ïó ¡£ +

+ +

+¿É ÒÔ Àû Óà Õâ žö ÊÖ ¶Î ÖŽ ÐÐ ²» ͬ ¶Ô Ïó ÉÏ µÄ ž÷ ÖÖ ²Ù ×÷£¬ +È» ¶ø PostgreSQL µÄ CREATE OR REPLACE Óï ·š ¶Ô ÓÚ ±à Œ­ ÊÓ ÍŒ¡¢ Žæ Ž¢ ¹ý ³Ì ºÍ º¯ Êý µÄ ¶š Òå ÈÔ È» ÌØ ±ð ÓÐ Óᣠ+

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/autovacuum.html (revision 1448) @@ -0,0 +1,25 @@ + + + + + +Guru Hints + + + + +

ÍÆŒöÔËÐÐpg_autovacuum

+

+pg_autovacuum ÒÔ Ç° ÊÇ Ò» žö Íâ ²¿ ·þ Îñ œø ³Ì£¬ PostgreSQL 8.1 ¿ª ÊŒ ÒÑ Ÿ­ ±» Õû ºÏ œø Êý ŸÝ ¿â ºó Ìš£¬ +Ëü œ« ÔÚ ±» ÐÞ žÄ µÄ Êý ŸÝ ×Ü Êý Žï µœ Öž ¶š Öµ ÒÔ ºó ×Ô ¶¯ ÔË ÐÐ VACUUM¡£ +

+

+ÔÚ PostgreSQL ·þ Îñ Æ÷ ÉÏ ÔË ÐÐ VACUUM ±£ ³Ö Êý ŸÝ Íê Õû ºÍ ·þ Îñ Æ÷ Ч ÂÊ ÊÇ Ç¿ ÖÆ Òª Çó£¬ +ÍÆ Œö Íš ¹ý ÔÚ postgresql.conf ÎÄ Œþ ÖÐ Éè Öà 'autovacuum'¡¢'stats_start_collector' ºÍ 'stats_row_level' ²Î Êý Ϊ 'on' ÀŽ ¿ª Æô pg_autovacuum ÊØ »€ ³Ì Ðò¡£ +×· ×Ù Êý ŸÝ ±ä »¯ ʱ ¶Ô ÐÔ ÄÜ »á ÓÐ Çá ΢ µÄ Ó° Ï죬 µ« ÊÇ ×Ü Ìå ÀŽ œ²£¬ Äã œ« ŽÓ ×Ô ¶¯ ÔË ÐÐ VACUUM ÖÐ »ñ µÃ žü ¶à Òæ ŽŠ¡£ +

+

+Ϊ ÌØ Êâ Ðè Çó µ÷ Õû pg_autovacuum µÄ ÖŽ ÐУ¬ ¿É ÒÔ ÐÞ žÄ postgresql.conf µÄ È« ŸÖ ²Î Êý »ò Õß Ä³ žö Êý ŸÝ ±í µÄ žö ±ð Éè Ö㬠Çë ²Î ÔÄ ÎÄ µµ¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/conn-listen.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Guru Hints + + + + +

·þÎñÆ÷ûÓÐœøÐÐŒàÌý

+

+·þ Îñ Æ÷ ÎÞ ·š œÓ ÊÜ Á¬ œÓ£º ÓÉ Á¬ œÓ ¿â ±š žæ +

+

+ +

+

+Èç ¹û ¿Ž µœ Õâ žö Ïû Ï¢£¬ Çë Œì ²é Õý ÔÚ ÊÔ ÍŒ Á¬ œÓ µÄ ·þ Îñ Æ÷ ÊÇ ·ñ ÔÚ Öž ¶š ¶Ë ¿Ú Ï ÔË ÐÐ PostgreSQL£¬ +ʹ Óà ping »ò Õß Ïà ËÆ ¹€ Ÿß Œì ²é ¿Í »§ ¶Ë µœ ·þ Îñ Æ÷ Ö÷ »ú Ö® Œä ÊÇ ·ñ Žæ ÔÚ Íø Âç Á¬ œÓ£¬ +Äã µÄ ÍøÂç / VPN / SSHÍšµÀ / ·À»ðÇœ ÊÇ ·ñ Õý È· Éè Öᣠ+

+

+³ö ÓÚ °² È« Ô­ Òò£¬ PostgreSQL ×î ³õ ²»»á Œà Ìý ·þ Îñ Æ÷ µÄ Ëù ÓÐ ÓРЧ IP µØ Ö·£¬ +Ϊ ÁË ÄÜ ¹» Íš ¹ý Íø Âç Á¬ œÓ Êý ŸÝ ¿â£¬ Ê× ÏÈ Ðè Òª Éè Öà Ëü ÄÜ ¹» Œà Ìý Ïà ÓŠ µØ Ö·¡£ +

+

+ŽÓ PostgreSQL 8.0 ¿ª ÊŒ£¬ ¿É ÒÔ ÔÚ postgresql.conf ÎÄ Œþ ÖÐ Óà "listen_addresses" ²Î Êý ¿Ø ÖÆ Œà Ìý¡£ +¿É ÒÔ ÔÚ Õâ Àï Êä Èë Ò» žö ÓŠ žÃ ±» Œà Ìý µÄ IP µØ Ö· ÁÐ ±í£¬ »ò Õß Óà '*' ±í ÊŸ Œà Ìý Ëù ÓÐ ÓРЧ µØ Ö·¡£ +¶Ô ÓÚ ±È œÏ Ôç µÄ °æ ±Ÿ £š7.3 »ò Õß 7.4£©£¬ Ðè Òª œ« "tcpip_socket" ²Î Êý Éè Öà Ϊ 'true'¡£ +

+

+¿É ÒÔ Ê¹ Óà ÔÚ pgAdmin III ÖÐ Õû ºÏ µÄ postgresql.conf ±à Œ­ Æ÷ ÀŽ ±à Œ­ postgresql.conf Åä Öà ÎÄ Œþ£¬ +ÐÞ žÄ Õâ žö ÎÄ Œþ Ö® ºó£¬ Ðè Òª ÖØ Ð Æô ¶¯ Êý ŸÝ ¿â œø ³Ì ʹ Éè Öà ÓРЧ¡£ +

+

+Èç ¹û ¶à ŽÎ Œì ²é Åä Öà ֮ ºó ÈÔ È» µÃ µœ Õâ žö Ží Îó ЊϢ£¬ ¿É ÄÜ ÊÇ Óö µœ ÁË Ò» žö Ö Ãü µÄ PostgreSQL Ží Îó£¬ +»ò Õß ¿É ÄÜ ÊÇ µÍ ²ã Íø Âç Á¬ œÓ ÎÊ Ìâ £š±È Èç ·À »ð Çœ µÄ Éè Öã©£¬ ÔÚ Ïò PostgreSQL ÍÅ Ìå Ìá œ» bug ±š žæ Ö® Ç° Çë ×Ð Ïž Œì ²é¡£ +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/fki.html (revision 1448) @@ -0,0 +1,34 @@ + + + + + +Guru Hints + + + +

ÍâŒüÒÔŒ°ËüµÄË÷Òý

+

+Íâ Œü ±» Óà ÀŽ ʹ Óà Âß Œ­ ·œ Êœ ¹Ø Áª Áœ žö Êý ŸÝ ±í£¬ Ê© ŒÓ žø Ëü ÃÇ ÏÞ ÖÆ Êý ŸÝ ±ä »¯¡£ +

+

+Õâ Ò» ÇÐ ¿ª ÊŒ ÓÚ Ö÷ Êý ŸÝ ±í£¬ Ëü ×÷ Ϊ ±» ²Î ¿Œ ±í£¬ Ðè Òª ÓÐ Ò» žö Ö÷ Œü £šµ± È»£¬ ʵ ŒÊ ÉÏ ±» ²Î ¿Œ ÁÐ Ö» Òª ·Ç ¿Õ ²¢ ÇÒ ÓРΚ Ò» Ë÷ Òý Ò² ÊÇ ¿É ÒÔ µÄ£¬ µ« ÊÇ Ê¹ Óà Ö÷ Œü ÈÔ È» ÊÇ œÏ ºÃ µÄ ·œ Êœ£©¡£ +ŽÓ ±í ÒÀ Àµ ÓÚ Ö÷ ±í£¬ žü РºÍ ²å Èë ʱ Óµ ÓÐ Íâ Œü µÄ ×Ö ¶Î Êý ŸÝ ±Ø Ðë ·û ºÏ Ö÷ ±í µÄ Êý ŸÝ£¬ ŽÓ ±í ÊÇ Íâ Œü µÄ ²Î ¿Œ ±í¡£ +

+

+Íâ Œü ²» œö ÏÞ ÖÆ ²Î ¿Œ ±í£¬ Ò² ÏÞ ÖÆ ±» ²Î ¿Œ ±í£¬ ÏÞ ÖÆ ·œ Êœ ¿É ÒÔ ÊÇ RESTRICT¡¢ CASCADE »ò SET NULL¡£ +Õâ Òâ ζ ×Å£¬ µ± ±» ²Î ¿Œ ±í Êý ŸÝ ·¢ Éú ±ä »¯ £šžü Р»ò ÉŸ ³ý£© ʱ£¬ Ëù ÓÐ µÄ ²Î ¿Œ ±í ¶Œ »á Œì ²é Êý ŸÝ ÊÇ ·ñ ºÏ Àí£¬ ÒÔ Œ° ÊÇ ·ñ Ðè Òª Æä Ëû žœ ŒÓ ²Ù ×÷¡£ +²é ÔÄ PostgreSQL ¹Ø ÓÚ Íâ Œü µÄ ÎÄ µµ ¿É ÒÔ ÕÒ µœ žü ¶à Ïž œÚ¡£ +

+

+±» ²Î ¿Œ ±í µÄ ÌØ ¶š ÐÐ Êý ŸÝ ·¢ Éú ±ä »¯ ʱ£¬ Ëù ÓÐ Ïà ¹Ø µÄ ²Î ¿Œ ±í ¶Œ »á ʹ Óà Íâ Œü ×Ö ¶Î ×÷ Ϊ Ìõ Œþ ÖŽ ÐÐ Ïà ÓŠ µÄ ¶Á ²Ù ×÷¡£ +Òò ŽË£¬ ËùÓÐ Ìá žß ¶Á È¡ Ч ÂÊ µÄ Éè ŒÆ Ô­ Ôò Ò² ÊÊ Óà ÓÚ ²Î ¿Œ ±í ×Ö ¶Î¡£ Ϊ ÁË ÓÐ ÁŒ ºÃ µÄ ÖŽ ÐРЧ ÂÊ£¬ Žó ¶à Êý Çé ¿ö Ï œš Á¢ Ë÷ Òý ÊÇ Ã÷ ÖÇ µÄ Ñ¡ Ôñ¡£ +PostgreSQL ²¢ û ÓÐ Ç¿ ÆÈ Õâ Ñù ×ö£¬ Ðè Òª Êý ŸÝ ¿â Éè ŒÆ ÈË Ô± ÀŽ Ìá ¹© ºÏ Àí µÄ Ë÷ Òý¡£ +

+

+Ϊ ÁË ·œ ±ã£¬ pgAdmin III ÔÚ ŽŽ œš Íâ Œü ʱ Ìá ¹© Ò» žö Œò ±ã µÄ checkbox£¬ ×Ô ¶¯ Œì ²é ÊÇ ·ñ ÓÐ ºÏ Àí µÄ Ë÷ Òý Žæ ÔÚ£¬ Èç ¹û û ÓÐ Ôò œš Á¢ Ò» žö¡£ +Èç ͬ Ëù ÓÐ Æä Ëü Ë÷ Òý Ò» Ñù£¬ ÓÐ Œ« ÉÙ Êý µÄ Çé ¿ö ·Ž ¶ø œµ µÍ ×Ü Ìå ÖŽ ÐРЧ ÂÊ£¬ ×Ü µÃ ÀŽ ˵£¬ Ë÷ Òý Ì« ÉÙ ±È Ë÷ Òý Ì« ¶à ¶Ô ÐÔ ÄÜ µÄ Ó° Ïì žü Žó¡£ +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,19 @@ + + + + + +Guru Hints + + + + +

Win32·þÎñÆ÷Ö®ÉϵÄUnicode±àÂë

+

+Êý ŸÝ ¿â ʹ Óà Unicode£šUTF8£© ±à Âë ÀŽ ±£ Žæ ºÍ ²Ù ×÷ ÔË ÐÐ ÓÚ Win32 ·þ Îñ Æ÷ Ö® ÉÏ µÄ PostgreSQL 8.0 ·þ Îñ Æ÷ Êý ŸÝ¡£

+

+Òò Ϊ ²Ù ×÷ ϵ ͳ û ÓÐ Ìá ¹© ×ã ¹» µÄ Ö§ ³Ö£¬Win32 Ö® Ï µÄ PostgreSQL 8.0 ÎÞ ·š ÒÀ ŸÝ ÊÊ µ± µÄ ŽÎ Ðò ¶Ô ×Ö ·û Ž® œø ÐÐ ÅÅ Ðò¡£

+

+Õë ¶Ô µ± Ç° °² ×°£¬ ÍÆ Œö ʹ Óà ±Ÿ µØ »¯ ±à Âë¡¢ ÔÚ ²» ͬ ²Ù ×÷ ϵ ͳ Ö® ÉÏ ÔË ÐÐ »ò Õß œ« Êý ŸÝ ¿â Éý Œ¶ µœ ÓРך ÃÅ Žú Âë ¿É ÒÔ Ö§ ³Ö Unicode ÅÅ Ðò µÄ PostgreSQL 8.1¡£

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/pk.html (revision 1448) @@ -0,0 +1,21 @@ + + + + + +Guru Hints + + + + +

Ö÷Œü

+

+µ± Éè ŒÆ Êý ŸÝ ±í µÄ ʱ ºò£¬ ±Ø Ðë ʱ ¿Ì ¹Ø ×¢ œñ ºó Èç ºÎ ÔÚ ±í ÖÐ ¶š λ Êý ŸÝ Žó ¶à Êý Çé ¿ö Ï£¬ Ðè Òª Óà һ žö ±ê ʶ ·û Κ Ò» ÐÔ µØ ¶š λ Ò» ÐÐ Êý ŸÝ£¬ Õâ žö ±ê ʶ ·û ÓŠ žÃ ×÷ Ϊ Ö÷ Œü ŽŠ Àí¡£ Ö÷ Œü ²» ±Ø Ö» °ü º¬ µ¥ Ò» µÄ ×Ö ¶Î£¬ ¿É ÒÔ °ü º¬ ¶à žö ±Ø Ðè ×Ö ¶Î Óà ÀŽ ±ê ʶ ij ÐÐ Êý ŸÝ¡£ Èç ¹û Ðè Òª Óà ¶à žö ×Ö ¶Î £šžù ŸÝ Ÿ­ Ñé £º Žó ÓÚ 3£© œš Á¢ Ö÷ Œü£¬ Ôö ŒÓ Ò» žö ²É Óà žü ŒÓ ·œ ±ã Àà ÐÍ £š±È Èç £º serial »ò Õß bigserial£© µÄ ×Ö ¶Î ×÷ Ϊ Ö÷ Œü ¿É ÄÜ ÊÇ žö ºÃ Ö÷ Òâ¡£

+

+Ö» ÓÐ Œ« ÉÙ Êý Çé ¿ö Ï£¬ Ö÷ Œü ²Å ÊÇ ÎÞ ¹Ø œô Òª µÄ¡£ Õâ Òâ ζ ×Å£º Ò» žö ÒŠʧ µÄ Ö÷ Œü Ç¿ ÁÒ °µ ÊŸ ×Å Õâ žö Êý ŸÝ ±í û ÓÐ Íê È« Éè ŒÆ Íê ±Ï¡£ Õâ Ò² ÊÇ Îª ʲ ÃŽ Guru Hint »á ÔÚ ŽŽ œš û ÓÐ Ö÷ Œü µÄ ±í ʱ Ìá ÊŸ Äã µÄ Ô­ Òò¡£

+

+Èç ¹û Äã ²é ¿Ž PostgreSQL µÄ ϵ ͳ ±í£¬ »á ·¢ ÏÖ Ëü ÃÇ ¶Œ û ÓÐ Ö÷ Œü£¬ Ϊ ʲ ÃŽ »á Õâ Ñù£¿ ʵ ŒÊ ÉÏ£¬ Ëù ÓÐ Õâ Щ ±í ¶Œ ÓÐ Ò» žö »ò Õß Áœ žö ²» ÔÊ Ðí Ϊ 0¡¢ ÄÜ ¹» ±» Ë÷ Òý ¿ì ËÙ ·Ã ÎÊ¡¢ ÄÜ ¹» Κ Ò» ±ê ʶ ÿ Ò» ÐÐ µÄ ×Ö ¶Î £šÍš ³£ Ö» ÓÐ OID£©£¬ ×ñ Ñ­ Ö÷ Œü µÄ µÚ ¶þ žö Ô­ Ôò ¡£ ÔÚ Õâ Àï ʹ Óà OID ÓÐ Àú Ê· ÐÔ Ô­ Òò£¬ Ëü ²» ÊÇ Éè ŒÆ Óà »§ ±í µÄ µÚ Ò» Ñ¡ Ôñ ¡£ Ëä È» ÓÐ ÏÔ Êœ Ö÷ Œü Õâ ÖÖ žü Рžü ºÏ ÊÊ µÄ ·œ Êœ£¬PostgreSQL Ϊ ÁË ±£ ³Ö ÁŒ ºÃ µÄ Ïò ºó Œæ ÈÝ ÐÔ ÈÔ È» ʹ Óà ŸÉ µÄ ·œ Êœ¡£

+

+Õý Èç ϵ ͳ ±í µÄ Àý ×Ó Ëù ÊŸ£¬ ¿ì ËÙ ·Ã ÎÊ ºÍ ±£ ³Ö Κ Ò» ÐÔ µÄ Ä¿ ±ê ¿É ÒÔ Íš ¹ý Æä Ëû ·œ Êœ Žï µœ£¬ ¶ø ²» ÊÇ ²É Óà Ö÷ Œü¡£ µ« ÊÇ£¬ Ϊ ÁË Ê¹ Êý ŸÝ Ä£ ÐÍ žü ŒÓ Çå Îú£¬ ÎÒ ÃÇ ÈÔ È» Ç¿ ÁÒ ÍÆ Œö ʹ Óà Ö÷ Œü ÀŽ Žï ³É Õâ Ò» Ä¿ ±ê¡£

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/saving-passwords.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/saving-passwords.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/saving-passwords.html (revision 1448) @@ -0,0 +1,17 @@ + + + + + +Guru Hints + + + + +

±£ŽæÃÜÂë

+

+Ÿ¯ žæ£º Äã ÒÑ Ÿ­ Ñ¡ Ôñ ÁË ±£ Žæ ÃÜ Â룬 ÔÚ *nix Ï Ëü œ« ±» ±£ Žæ ÔÚ home Ä¿ ÂŒ µÄ Ž¿ ÎÄ ±Ÿ ÎÄ Œþ ÖУ¬ ¶ø ÔÚ Windows ϵ ͳ Ï Ëü œ« ±» ±£ Žæ ÔÚ Óà »§ µÄ Åä Öà ÎÄ Œþ ÖС£ Èç ¹û Äã ²» Ïë Õâ ÃŽ ×ö£¬ Çë µã »÷ Cancel °Ž Å¥¡£

+

+pgAdmin ʹ Óà PostgreSQL µÄ 'pgpass' »ú ÖÆ ±£ Žæ ÃÜ Âë¡£ ÔÚ *nix ϵ ͳ Ï£¬ ÃÜ Âë œ« ±» ±£ Žæ ÔÚ ~/.pgpass ÎÄ Œþ ÖУ» ¶ø ÔÚ Windows ϵ ͳ Ï£¬ Ëü œ« ±» ±£ Žæ ÔÚ %APPDATA%\PostgreSQL\pgpass.conf ÎÄ Œþ ÖÐ £š%APPDATA% ÊÇ Î» ÓÚ Óà »§ Åä Öà ÎÄ Œþ Ö® ÄÚ µÄ 'Application Data' ÎÄ Œþ ŒÐ£©¡£ Õâ žö »ú ÖÆ ±» Óà ÀŽ ×÷ Ϊ ʹ Óà libpg ¿â Á¬ œÓ Êý ŸÝ ¿â ·þ Îñ Æ÷ µÄ Ëù ÓÐ ³Ì Ðò µÄ ȱ Ê¡ »ú ÖÆ£¬ °ü Àš Ãü Áî ÐÐ ³Ì Ðò£šÀý Èç pg_dump ºÍ pg_restore£©¡¢ Æä Ëû GUI ³Ì Ðò¡¢ Çý ¶¯ ³Ì Ðò £šÀý Èç £º psqlODBC£©¡£ Õâ Òâ ζ ×Å Õâ Щ ³Ì Ðò ¶Œ ¿É ÒÔ Ê¹ Óà Õâ žö ±£ Žæ µÄ ÃÜ Âë ×Ô ¶¯ Á¬ œÓ µœ Êý ŸÝ ¿â£¬ Èç ¹û Äã ²» Ïë Õâ Ñù ×ö£¬ ²» Òª ʹ Óà pgAdmin µÄ Store Password µÄ Ñ¡ Ïî¡£

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/hints/multiple.html (revision 1448) @@ -0,0 +1,12 @@ + + + + + +Guru Hints + + +

+pgAdmin III ·¢ ÏÖ µ± Ç° ¶Ô Ïó ÓÐ ¶à žö œš Òé¡£

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_CN/tips.txt (revision 1448) @@ -0,0 +1,78 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +PostgreSQL的执行效率可以通过定期对数据库进行空闎回收埗到提高。 +PostgreSQL官方生日是7月8号项目匀始于1996幎。 +原始pgAdmin项目的第䞀䞪原型叫做pgManager是䞺PostgreSQL 6.3.2猖写的。 +pgAdmin的技术支持可以通过邮件列衚pgadmin-support@postgresql.org获埗。 +pgAdmin的匀发成员们通过邮件列衚pgadmin-hackers@postgresql.orgè®šè®ºæ–°ç‰¹æ€§å’ŒåŒ€å‘æƒ +况。 +pgAdmin II䜿甚的pgSchema库倧郚分是圚牛接附近的䞀台电视机前甚Windows 2000笔记本匀发的。 +可以䜿甚“文件”菜单的“变曎密码”来修改密码。 +SQL窗栌星瀺选䞭对象的反向SQL语句。 +42是生呜、宇宙和䞇物的终极解答。 +pgAdmin的匀发人员分垃圚英囜、法囜、執囜、意倧利和矎囜。 +䞺了减少OID的䜿甚从PostgreSQL 7.2匀始支持没有OID列的衚。 +䜿甚状态工å +·å¯ä»¥åŸºäºŽæ¯äž€äžªè¿žæŽ¥ç›‘视系统掻劚。 +圚源代码树的/contrib目圕䞋有讞倚有甚的文件、工å +·å’Œæ–¹æ¡ˆã€‚ +PostgreSQLçš„å­˜å‚šè¿‡çš‹è¯­èš€åŒ +括pl/pgSQL、pl/Python、pl/TCL、pl/Perl和pl/sh。 +pgAdmin II圚第䞀䞪å +·æœ‰æ­£åŒç‰ˆå“èŽšçš„版本发垃*以前*å°±æœ‰è¶ +过10,000次的䞋蜜。 +pgAdmin II第䞀䞪皳定版本圚它发垃后的6äžªæœˆä¹‹å† +è¢«äž‹èœœè¶ +过35,000次。 +来自gborg.postgresql.org的Slony-I可以甚来做䞻从数据库倍制。 +pgAdmin II的第䞀䞪官方皳定版本是圚2002幎1月16号发垃的。 +pgAdmin III项目的匀发匀始于2002幎9月29号。 +pgAdmin III是䞀䞪基于wxWidgets匀发框架䜿甚C++猖写的å +šæ–°ç‰ˆæœ¬ïŒŒå¯ä»¥è¿è¡ŒåœšWindows和*nix系统之䞊。 +pgAdmin是基于匀攟源码的'Artistic协议'发垃的。 +PostgreSQL 7.3可以支持方案schemaïŒ‰ïŒŒå®ƒæ˜¯æ•°æ®åº“ä¹‹å† +的独立呜名空闎。 +域可以甚来创建䞀䞪基于普通基本类型的预定义数据类型。 +pgAdmin III 1.0.0圚2003幎9月26å·æ‰“åŒ +发垃。 +劂果列数据类型䞍笊合PostgreSQL的planner将跳过指定的玢匕扫描。 +䞍芁䜿甚'kill -9'呜什å +³é—­postmaster进皋。 +䌘化SQL查询时“EXPLAIN ANALYZE”呜什和“解析查询”按钮是䜠的奜朋友。 +PostgreSQL 8.0å¢žåŠ çš„äž»èŠæ–°ç‰¹æ€§ïŒŒåŒ +æ‹¬ïŒšä¿å­˜ç‚¹ã€è¡šç©ºé—ŽïŒŒä»¥åŠå€§å®¶é•¿ä¹ +ç­‰åŸ +的Windows版本。 +pgAdmin III支持SSL加密连接。 +新的Win32版PostgreSQL第䞀次通过它的回園测试是圚2004幎10月24号。 +Windows版PostgreSQL圚它最初发垃的5å€©ä¹‹å† +è¢«äž‹èœœè¶ +过45,000次。 +“给目前还没有创建的对象讟眮ACL时没有䜿ok按钮有效”的bug是圚芬å +°äžŠç©º39,000英尺的地方由Andreas、Magnus和Dave修正的圓时他们正圚从日本的Slony-I和pgAdmin III展瀺䌚返回途䞭。 +䞺PostgreSQL讟眮过倚的å +±äº«çŒ“å­˜å¯èƒœç»™æ‰§è¡Œæ•ˆçŽ‡åžŠæ¥èŽŸé¢åœ±å“ïŒŒå› äžºå®ƒå‡å°‘äº†æ“äœœç³»ç»Ÿå† +æ žæ–‡ä»¶çŒ“å†²ç©ºé—Žçš„å¯ç”šå† +存。 +持续坐12小时板凳真地䌚什人厌烊而䞔倎脑麻朚这就是䞺什么我现圚写新小秘诀的原因。 +日本PostgreSQL甚户团䜓JPUGïŒ‰å·²ç»æœ‰è¶ +过5000的成员并䞔还圚持续增长。 +pgAdmin 1.4äžŽä»¥å‰çš„ç‰ˆæœ¬ç›žæ¯”æ”¯æŒæ›Žå€šçš„å¹³å°ïŒŒåŒ +括䌗倚Linux版本、Microsoft Windows(tm)、FreeBSD、Solaris和Mac OS X。 +pgAdmin 1.4åŒ +含了䞀䞪囟圢化的EXPLAINå·¥å +·ïŒŒå¯ä»¥ç”šæ¥æ›Žå®¹æ˜“åœ°é˜ +读和理解查询计划。 +pgAgent可以甚来䞺有规埋执行的批倄理和SQLäœœäžšåˆ¶å®šè®¡åˆ’è¡šïŒŒäŸ‹åŠ‚é‡å»ºæ•°æ®æ•æ„Ÿçš„å±€éƒšçŽ¢åŒ•ã€æ—§çºªåœ•çš„æž +陀。 +äœ¿ç”šå‡œæ•°æˆ–è€ +视囟将应甚皋序逻蟑攟进数据库是䞀䞪奜的习惯这样胜借确保产品的䞍同客户端总是看到盞同的数据视囟并䞔总是䜿甚盞同的逻蟑来曎新数据。劂果䞍这样做䜠䞍埗䞍把逻蟑圚每䞀䞪客户端䞊实现䞀次。 +䞺了提高数据库的安å +šæ€§ïŒŒåˆ›å»ºpg_hba.conf时最小化可以访问数据库的远皋䞻机的数量并䞔总是䜿甚加密连接陀非䜠有曎奜的理由䞍这样做。 +å¯ä»¥é€šè¿‡æ‹’ç»äž€äžªç”šæˆ·æˆ–è€ +ç»„è®¿é—®æŸäžªè¡šïŒŒè€Œå»ºç«‹äž€äžªå®ƒå¯ä»¥è®¿é—®çš„åªåŒ +å«å®ƒåº”è¯¥çœ‹åˆ°å­—æ®µçš„è§†å›Ÿæ¥é™åˆ¶ç”šæˆ·æˆ–è€ +组访问特定字段。劂果甚户需芁曎新基衚数据可以创建䞀䞪将曎新从视囟应甚到衚䞊的规则来实现。 +PostgreSQL可以运行圚匂种平台之䞊䟋劂埮蜯的X-Box、玢尌的PlayStation II以及倏普的Zaurus PDA。 +EnterpriseDB捐赠了䞀台Apple Powerbook给pgAdmin项目甚来提升pgAdmin圚Mac OS X系统䞊的品莚和他们简化过的掟生产品EDB Studio。 Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/it_IT/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/it_IT/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/it_IT/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +Le performance di PostgreSQL possono migliorare se si effettua periodicamente il VACUUM dei database. +La data ufficiale di nascita di PostgreSQL Ú l'otto luglio. Il progetto PostgreSQL naque nel 1996. +Il primo prototipo del progetto pgAdmin si chiamava pgManager e fu scritto per PostgreSQL 6.3.2. +Il supporto per pgAdmin può essere richiesto tramite la lista di messaggi pgadmin-support@postgresql.org. +Le nuove funzionalità e lo sviluppo sono discussi dagli sviluppatori di pgAdmin sulla lista pgadmin-hackers@postgresql.org. +La maggior parte della libreria pgSchema usata da pgAdminII fu sviluppata con un portatile con windows 2000 davanti la TV vicino Oxford, in Inghilterra. +Si può cambiare la password selezionando «Cambia password» dal menu «File». +Il quadro «definizione» mostra il comando SQL che potrebbe essere utilizzato per creare l'oggetto selezionato. +La risposta alla domanda sulla vita, l'universo e tutto quanto Ú 42. +Il nocciolo degli sviluppatori di pgAdmin Ú basato in UK, Francia, Germania, Italia e USA. +Dalla versione PostgreSQL 7.2 sono supportate tabelle senza la colonna OID per cercare di diminuire l'utilizzo degli OID. +Si può controllare l'attività di sistema a livello della singola connessione tramite lo strumento di «stato». +Ci sono parecchi file, strumenti e progetti utili nella directory contrib/ dei sorgenti di PostgreSQL. +I linguaggi procedurali di PostgreSQL sono pl/pgSQL, pl/Python, pl/TCL, pl/Perl e pl/sh. +pgAmin II fu scaricato oltre 10.000 volte *prima* che fosse il completo il controllo qualitativo! +La prima versione stabile di pgAdmin II fu scaricata oltre 35.000 volte nei primi 6 mesi successivi al rilascio. +Il progetto Slony-I da www.slony.info può essere utilizzato per la replicazione Master->Slave. +La prima versione ufficiale stabile di pgAdmin II fu rilasciata il 16 gennaio 2002. +Lo sviluppo del progetto pgAdmin III cominciò il 28 settembre 2002. +pgAdmin III Ú una versione di pgAdmin scritta completamente in C++ usando il framework wmWidgets per poter girare su Windows e sistemi Unix. +pgAmin Ú rilasciato sotto la «artistic licence». +PostgreSQL 7.3 supporta gli schemi che sono degli spazi con un nome all'interno dei database. +I domini possono essere utilizzati per creare dei tipi di dato predefiniti a partire dai tipi base. +pgAdmin III 1.0.0 fu rilasciato il 26 settembre 2003. +Il pianificatore di PostgreSQL ignorerà il desiderio di fare una scansione dell'indice se i tipi delle colonne usate per la join non corrispondono. +Non si dovrebbe «kill -9» il postmaster!! +I bottoni «explain analyze» e «explain query» sono tuoi amici quando si deve ottimizzare una interrogazione. +PostgreSQL 8.0 aggiunse parecchie nuove funzionalità al nostro DBMS, inclusi i punti di salvataggio, i tablespace e il tanto atteso port per Windows. +pgAdmin III supporta le connessioni cifrate SSL. +Il nuovo port PostgreSQL per Win32 ha passato tutti i test per la prima volta il 24 ottobre 2004. +Il port di PostgreSQL per windows fu scaricato oltre 45.000 volte nei primi cinque giorni dal rilascio! +Il bug «non abilitare il bottone OK quando si impostano le ACL per oggetti non ancora creati» Ú stato risolto a 39000 piedi d'altezza sopra la Finlandia mentre Andreas, Magnus e Dave stavano tornando dalla presentazione in Giappone di Slony-I e pgAdmin III! +Impostare troppy «shared buffer» in PostgreSQL può avere effetti peggiorativi sulle performance perché riduce la quantità di RAM dispobile per il kernel del sistema operativo che la usarebbe come cache del file system. +Sedere s un un aereo per 12 ore Ú veramente noioso ed Ú i lmotivo per quale sto scrivendo i suggerimenti proprio adesso!! +Il gruppo degli utenti PostgreSQL giapponesi o JOUG ha oltre 5000 membri e cresce in continuazione. +pgAdmin 1.4 Ú supportato su più piattaforme che qualsiasi suo predecessore, incluse varie distribuzioni Linux, Microsoft Windows (tm), FreeBSD, Solaris e Mac OS X. +pgAdmin 1.4 include uno strumento «explain» grafico che permette di leggere i capire facilmente i piani di esecuzione. +pgAgent può essere utilizzato per schedulare delle operazioni SQL periodiche come la ricreazione di indici parziali o la cancellazione di vecchi record. +Costruire la logica applicativa all'interno del detabase tramite funzioni e viste Ú una buona pratica. Questo assicura che che i vari clienti del prodotto avranno sempre le stesse viste dei dati e li modificheranno allo stesso modo. Ancora meglio: va scritto solo una volta per tutti i clienti! +Minimizzare l'ammontare degli accessi permessi a host remoti quando di si crea il file pg_hba.conf per aiutare a mantenere sicuro il database, e utilizzare sempre connessioni cifrate a meno che non ci sia una motivazione valida per non farlo. +Si può restringere l'accesso a specifiche colonne di una tabella a un utente particolare o un gruppo, vietandogli l'accesso diretto e creando una vista che contiene solo le colonne della tabella che vedrebbero. Se l'utente deve anche aggiornare i dati si possono creare le regole per l'aggiornamento della tabella sottostante tramite la vista. +PostgreSQL Ú stato fatto girare sulle piattaforme più diverse, come la X Box della Microsoft, la PlayStation II della Sony, il PDA Zaurus della Sharp! +EnterpriseDB ha donato un Powerbook Apple al progetto pgAdmin per aiutare a migliorare il port su Mac OS X di pgAdmin e del loro prodotto derivato, EDB Srudio. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhp =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhp (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhp (revision 1448) @@ -0,0 +1,65 @@ +[OPTIONS] +Compatibility=1.1 or later +Compiled file=pgadmin3.chm +Contents file=pgadmin3.hhc +Default topic=index.html +Display compile progress=Yes +Full-text search=Yes +Language=0x409 English (United States) +Title=pgAdmin III + + +[FILES] +using.html +appendices.html +backup.html +bugreport.html +commandline.html +connect.html +connect-error.html +control-server.html +debugger.html +default-xsl.html +editgrid.html +export.html +extend.html +grantwiz.html +gridopts.html +guruhints.html +index.html +kerberos.html +licence.html +macros.html +main.html +maintenance.html +openssl.html +options.html +options-tab1.html +options-tab2.html +options-tab3.html +options-tab4.html +options-tab5.html +password.html +pgagent.html +pgagent-install.html +pgagent-jobs.html +pgagent-schedules.html +pgagent-steps.html +query.html +reports.html +restore.html +sample-xml.html +slony.html +slony-example.html +slony-execute.html +slony-functions.html +slony-install.html +slony-overview.html +slony-path.html +slony-set.html +status.html +team.html +translation_team.html + +[INFOTYPES] + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/sample-xml.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/sample-xml.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/sample-xml.html (revision 1448) @@ -0,0 +1,75 @@ + + + + + +Sample XML report data + + + + +

Sample XML report data

+ +

+The sample report below demonstrates the XML format that the pgAdmin +Report Tool will produce. +

+ +
+<?xml version="1.0" encoding="UTF-8"?>
+<?xml-stylesheet type="text/xsl" href="C:\stylesheet.xsl" ?>
+
+<report>
+
+  <header>
+
+    <!-- All the values in the header section are optional, apart from the title. -->
+
+    <title>Sample XML file</title>
+    <notes>This is a sample XML file.</notes>
+    <generated>10/05/2006 11:21:23</generated>
+    <server>localhost:5432</database>
+    <database>postgres</database>
+    <schema>public</schema>
+    <table>pg_ts_cfg</table>
+    <job></job>
+  </header>
+
+  <!-- Multiple report sections may be present, and must have a name -->
+
+  <section id="s1" number="1" name="Query results">
+  
+    <!-- A table is optional within a section. If present, the number -->
+    <!-- of columns should be appropriate for the attributes specified -->
+    <!-- in each row. A row needn't specify every value however. -->
+
+    <table>
+      <columns>
+        <column id="c1" number="1" name="oid" />
+        <column id="c2" number="2" name="ts_name" />
+        <column id="c3" number="3" name="prs_name" />
+        <column id="c4" number="4" name="locale" />
+      </columns>
+      <rows>
+        <row id="r1" number="1" c1="17108" c2="default" c3="default" c4="C" />
+        <row id="r2" number="2" c1="17109" c2="default_russian" c3="default" c4="ru_RU.KOI8-R" />
+        <row id="r3" number="3" c1="17110" c2="simple" c3="default" c4="" />
+      </rows>
+      
+      <!-- Additional section specific info may be supplied. -->
+
+      <info>3 rows with 4 columns retrieved.</info>
+
+    </table>
+    
+    <!-- Each section may also contain some related SQL. -->
+
+    <sql>SELECT oid, * FROM pg_ts_cfg</sql>
+
+  </section>
+
+</report>
+
+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab2.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab2.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab2.html (revision 1448) @@ -0,0 +1,58 @@ + + + + + +pgAdmin Options - Tab 2 (Preferences) + + + + +

pgAdmin Options - Tab 2 (Preferences)

+ +
+ +

+

+

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/export.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/export.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/export.html (revision 1448) @@ -0,0 +1,33 @@ + + + + + +pgAdmin Data Export + + + + +

pgAdmin Data Export

+ +
+ +

Data is written to a file, using the selected options.

+

The row separator option selects the character used to separate +rows of data. On Unix systems, usually a linefeed character (LF) is +used, on Windows system a carriage return/linefeed (CR/LF) +combination. +

The separarating character between columns can be selected +between colon, semicolon and a vertical bar.

+The individual columns can be enclosed in quotes. Quoting can be +applied to string columns only (i.e. numeric columns will not be +quoted) or all columns regardless of data type. The character used for +quoting can be a single quote or a double quote. +

+If the "Column names" option is selected, the first row of the +file will contain the column names. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,29 @@ + + + + + +Guru Hints + + + + +

Database encoding

+

+The database is created to store data using the SQL_ASCII encoding. This encoding is defined +for 7 bit characters only; the meaning of characters with the 8th bit set (non-ASCII characters 127-255) is not defined. +Consequently, it is not possible for the server to convert the data to other encodings. +

+

+If you're storing non-ASCII data in the database, you're strongly encouraged to use a proper +database encoding representing your locale character set to take benefit from the automatic conversion to different client encodings +when needed. If you store non-ASCII data in an SQL_ASCII database, you may encounter +weird characters written to or read from the database, caused by code conversion problems. +This may cause you a lot of headache when accessing the database using different +client programs and drivers. +

+

+For most installations, Unicode (UTF8) encoding will provide the most flexible capabilities. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-ident.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru Hints + + + + +

Ident authentication failed

+

+The server doesn't accept the current user: The server reports +

+

+ +

+

+If this message appears, the pg_hba.conf entry found for your client / user / database combination +is set to "ident" authentication. Some distributions, e.g. Debian, have this by default. +To perform ident based authentication successfully, you need additional setup; see the PostgreSQL +help for this. For a beginner, it might be more appropriate to use a different authentication method; +MD5 encrypted passwords are a good choice, which can be configured by an entry in pg_hba.conf like this: +

+

+host all all 192.168.0.0/24 md5 +

+

+This example grants MD5 encrypted password access to all databases to all users on the private network 192.168.0.0/24. +

+

+You can use the pg_hba.conf editor that is built into pgAdmin III to edit the pg_hba.conf +configuration file. After changing pg_hba.conf, you need to trigger a server configuration reload using pg_ctl or by +stopping and restarting the server process. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/vacuum.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + +Guru Hints + + + + +

Running VACUUM recommended

+

+The estimated rowcount on the table "" deviates significantly from the actual rowcount. +You should run VACUUM ANALYZE on this table. +

+Instead of issuing a manual VACUUM ANALYZE command on this table (you can use +the pgAdmin III maintenance menu for this), running VACUUM ANALYZE on a regular +or automated basis should be considered. This can be achieved using a scheduler. PostgreSQL also supplies +the pg_autovacuum daemon, which will track changes made to the database and issue +vacuum commands as required automatically. In most cases, pg_autovacuum will be the +best choice. +



+What is VACUUM good for? +

+The PostgreSQL query planner makes its decision based on assumptions, taken from +the estimated rowcount. If the actual rowcount is too different from the estimated rowcount, +the planner might take a wrong decision, resulting in a query plan that is not optimal. This might +result in poor performance. +

+The PostgreSQL storage needs VACUUM to have transaction IDs in tables fixed. +Additionally, outdated rows from updates and deletes are not cleaned up until the VACUUM +command has been issued on that table. In-depth information can be found in the online +documentation, just press the help button. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/instrumentation.html (revision 1448) @@ -0,0 +1,42 @@ + + + + + +Guru Hints + + + + +

Server instrumentation

+

+The server lacks instrumentation functions. +

+

+pgAdmin III uses some support functions that are not available by default +in all PostgreSQL versions. These enable some tasks that make life easier when +dealing with log files and configuration files. +

+

+When you install PostgreSQL 8.0 or up using the Windows installer, you just need to +select the "admin" or "adminpack" module.c +

+

+When compiling from source, the necessary files can be found in the xtra subdirectory +of the pgAdmin source tree. For PostgreSQL 8.0, copy the admin directory under +the postgresql contrib source directory, make and make install from there. For PostgreSQL 8.1, +use the admin81 directory for that. +

+PostgreSLQ 8.2 and above include the instrumentation functions in the "adminpack" contrib +module. +

+

+After the module is installed, you need to create the instrumentation functions in +your maintenance database using the admin.sql script (admin81.sql for PostgreSQL 8.1) +which are usually located in the pgsql share directory (e.g. /usr/local/pgsql/share) +

+

+Extended server instrumentation is not supported for PostgreSQL 7.3 and 7.4. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

Edit table data without primary key

+

+Since the table doesn't have a primary key or OIDs, you can view the data only. +Inserting new rows and changing existing rows isn't possible for the Edit Data tool without primary key. +

+

+In order to edit data, pgAdmin III requires a primary key on the table, which is a good database design practice anyway. +Alternatively, the table can be created WITH OIDS. Please note that oids are not guaranteed to be unique over a very +long period of time, so using oids as kind-of primary key is only second choice. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-hba.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +Guru Hints + + + + +

Access to database denied

+

+The server doesn't grant access to the database: the server reports +

+

+ +

+

+To access a database on a PostgreSQL server, you first have to grant primary access +to the server for your client (Host Based Authentication). PostgreSQL will check the pg_hba.conf file if a +pattern that matches your client address / username / database is present and enabled before any +SQL GRANT access control lists are evaluated. +

+

+The initial settings in pg_hba.conf are quite restrictive, in order to avoid unwanted security holes +caused by unreviewed but mandatory system settings. You'll probably want to add something like +

+

+host all all 192.168.0.0/24 md5 +

+

+This example grants MD5 encrypted password access to all databases to all users on the private network 192.168.0.0/24. +

+

+You can use the pg_hba.conf editor that is built into pgAdmin III to edit the pg_hba.conf +configuration file. After changing pg_hba.conf, you need to trigger a server configuration reload using pg_ctl or by +stopping and restarting the server process. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/object-editing.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/object-editing.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/object-editing.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Guru Hints + + + + +

Editing Views, Stored Procedures or Functions

+

+When editing the code for a view, stored procedure or function, instead of using the small +text box on the properties dialogue for the object, you might find it more convenient to +use the scripting options in pgAdmin to edit the object in the query tool. This gives you the +benefit of the Query Tool editor's features such as autocomplete, find and replace and larger +workspace. +

+ +

+To use the scripting options, in the pgAdmin browser window, right-click the object you wish +to edit, and select the CREATE script option. It may be on the Scripts submenu. +Alternatively, you can select the object and then choose the CREATE script option from +the Scripts submenu of the Tools menu. +

+ +

+Edit the definition of the object as required, and +use the Execute Query button to apply your changes. Don't forget that modifying a view +or function name, or the signature of a function or procedure may result in a new +object being created alongside the original one. This useful side effect makes it convenient +to create new, but similar objects. You may need to refresh the pgAdmin browser to display +newly created objects. +

+ +

+You can use this technique to perform all sorts of operations on different objects, however +PostgreSQL's CREATE OR REPLACE syntax makes it particularly useful for editing views, +stored procedures and functions. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/autovacuum.html (revision 1448) @@ -0,0 +1,30 @@ + + + + + +Guru Hints + + + + +

Running pg_autovacuum recommended

+

+Introduced in PostgreSQL 8.1, the pg_autovacuum process which was previously +implemented as an external service process is now integrated into the backend. It will +run VACUUM automatically if a configurable amount of data has changed. +

+

+Running VACUUM is mandatory on a PostgreSQL server to keep data consistent +and the server performant. As a start, it is recommended to enable the pg_autovacuum +daemon by setting 'autovacuum', 'stats_start_collector' and 'stats_row_level' +in postgresql.conf to 'on'. With a usually neglectable performance penalty from the +data change tracking, you will gain automatic performing VACUUM runs. +

+

+To adjust pg_autovacuum performance for individual needs, you might need to tune +its settings using global parameters in postgresql.conf, or individually on each table; see +the documentation. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/conn-listen.html (revision 1448) @@ -0,0 +1,45 @@ + + + + + +Guru Hints + + + + +

Server doesn't listen

+

+The server doesn't accept connections: the connection library reports +

+

+ +

+

+If you encounter this message, please check if the server you're trying to contact is actually +running PostgreSQL on the given port. Test if you have network connectivity from your +client to the server host using ping or equivalent tools. Is your network / VPN / SSH tunnel / +firewall configured correctly? +

+

+For security reasons, PostgreSQL does not listen on all available IP addresses on the server machine initially. In order to access +the server over the network, you need to enable listening on the address first. +

+

+For PostgreSQL servers starting with version 8.0, this +is controlled using the "listen_addresses" parameter in the postgresql.conf file. Here, you can enter a list of IP addresses +the server should listen on, or simply use '*' to listen on all available IP addresses. For earlier servers (Version 7.3 or 7.4), you'll need to +set the "tcpip_socket" parameter to 'true'. +

+

+You can use the postgresql.conf editor that is built into pgAdmin III to edit the postgresql.conf configuration file. +After changing this file, you need to restart the server process to make the setting effective. +

+

+If you double-checked your configuration but still get this error message, it's still unlikely +that you encounter a fatal PostgreSQL misbehaviour. You probably have some low level +network connectivity problems (e.g. firewall configuration). Please check this thoroughly +before reporting a bug to the PostgreSQL community. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/fki.html (revision 1448) @@ -0,0 +1,42 @@ + + + + + +Guru Hints + + + +

Foreign key covering indexes

+

+A foreign key is used to couple two tables in a logical way, and restrict the changes that can be applied to them. +

+

+It all starts with a master table, which will be the referenced table. It needs to have a primary key (well, actually the +referenced columns only need to be not null and covered by a unique index, but it's really good advice to have a +primary key). The slave table depends on the master table, in the sense that the columns on which +the foreign key is created must match the master table for any key inserted or updated. The slave table is the referencing +table of the foreign key. +

+

+The foreign key not only restricts the referencing table, but also the referenced table; the flavour of restriction can be +RESTRICT, CASCADE or SET NULL. This means, that if a row in the master/referenced table is changed (updated +or deleted), all referencing tables are checked if the operation is valid, and if there's some additional action to perform; +see the PostgreSQL documentation on foreign keys for further details. +

+

+This means that on change access to a specific row in the referenced table, a corresponding read is performed on all +referencing tables, using the foreign key columns as access key. Consequently, all design rules which should be taken +into account for good read performance usually also apply to columns in a referencing table. For good performance, +an index is advisable in most cases. PostgreSQL does not enforce this in any way, so it's up to the database designer +to provide an index. +

+

+For convenience, pgAdmin III provides a simple checkbox when creating a foreign key, which will automatically check +for the presence of a usable index, and will create one for you if none is found. As with all indexes, there are rare cases when such an index degrades your +overall performance a little, but in general having one index too few is much more performance degrading than having one +index too much. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,27 @@ + + + + + +Guru Hints + + + + +

Unicode encoding on a Win32 server

+

+The database is created to use Unicode (UTF8) encoding to store data and +is operated on a PostgreSQL 8.0 server running on a Win32 server. +

+

+The PostgreSQL 8.0 Win32 implementation is not able to sort character strings according +to appropriate collation sequences, because the operating system doesn't offer sufficient +support for this. +

+

+For this installation, it is recommended to use a locale specific encoding, run the cluster on +a different operating system or upgrade your database cluster to PostgreSQL 8.1 which has +additional code to deal with unicode collations to solve the issue. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/pk.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru Hints + + + + +

Primary keys

+

+When designing a table, you should always keep in mind how the table will be addressed +later. In most cases, you will need an identifier in order to uniquely address a specific +row; this identifier should be created as your primary key. A primary key needn't +necessarily consist of a single column; it may contain as many columns as necessary +to uniquely identify a row. If you need many columns (rule of thumb: more than 3), it might be a good +idea to invent an additional column with a convenient data type, e.g. serial or bigserial, which holds the primary key. +

+

+Only in rare cases it doesn't make sense to use a primary key. That means, a missing primary key is quite +a strong indicator for table not being designed completely; that's why a Guru Hint will arise if you create a table without +primary key. +

+

+If you look at PostgreSQL's system tables, you will find that none of them has a primary key, so what's this about? +Actually, all of these tables have one or two columns (usually OID only) which uniquely identifies each row, obeying the +second rule for a primary key, not allowing zero, and being covered by an index for faster access. Usage of OIDs has +historic reasons, and isn't really first choice for designing user tables. PostgreSQL still uses this for backwards compatibility, +and while a newer approach would probably use explicit primary keys it won't be changed now any more. +

+

+As the case of system tables shows, the goal of uniqueness and fast access can be achieved with other approaches than +a primary key. Still, for clarity of the data model, you're strongly encouraged to use primary keys for this purpose. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/saving-passwords.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/saving-passwords.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/saving-passwords.html (revision 1448) @@ -0,0 +1,26 @@ + + + + + +Guru Hints + + + + +

Saving passwords

+

+WARNING: You have opted to save your password. It will be stored in plain text in your home directory on *nix +systems, or in your user profile on Windows. If you do not want this to happen, please press the Cancel button. +

+

+pgAdmin uses PostgreSQL's 'pgpass' mechanism to store your passwords. On *nix systems, the password will be stored in +~/.pgpass, whilst on Windows systems it will be stored in %APPDATA%\PostgreSQL\pgpass.conf (%APPDATA% is the +'Application Data' folder in your user profile). This mechanism is used by default by all programs that use the libpq +library to access the server, which includes command line applications such as pg_dump and pg_restore, other GUI +applications, and drivers such as psqlODBC. This means that those applications may automatically connect to the +server using your stored password. If you do not want this to happen, you should not use the Store Password +option in pgAdmin. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Guru Hints + + +

+pgAdmin III has found multiple issues on the current object. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab4.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab4.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab4.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +pgAdmin Options - Tab 4 (Logging) + + + + +

pgAdmin Options - Tab 4 (Logging)

+ +
+ +

+

+

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/status.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/status.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/status.html (revision 1448) @@ -0,0 +1,105 @@ + + + + + +Database Server Status + + + + +

Database Server Status

+ +
+ +

+The Server Status dialogue displays the current connections to each +database, the user that is connected, the process ID, the client address +and start time (on PostgreSQL 8.1 and above), the current +query being executed (if any), and the query start time (where appropriate) +on PostgreSQL 7.4 and above on the Status tab. +

+

+The Cancel button allows cancelling the query running on a specific +backend. Terminate will shutdown the backend. Attention: Both functions should be +used carefully, as the interrupt the client's work +ungracefully. Particularly, the terminate function might disturb the +function of the complete server, force it to restart its services and +thus interrupt all user connections. You should use this function only +if the server is seriously injured by a backend you can't control otherwise. +

+

+

+
+

+The Locks tab shows the current locks outstanding in the PostgreSQL Lock +Manager. This information can be useful when attempting to debug or track +down deadlocks on your server. Not all information is necessarily shown +for each lock. In particular, the Relation name may be shown as an OID +instead of by it's name, if the relation is in a different database to +that being monitored. +

+

+The Cancel button allows cancelling the query running on a specific +backend. Terminate will shutdown the backend. Attention: Both functions should be +used carefully, as the interrupt the client's work +ungracefully. particularly, the terminate function might disturb the +function of the complete server, force it to restart its services and +thus interrupt all user connections. You should use this function only +if the server is seriously injured by a backend you can't control otherwise. +

+

+Note: When the pg_locks view is accessed as is the case whenever +this dialgue is open, PostgreSQL's internal lock manager data structures are +momentarily locked, and a copy is made for the dialogue to display. This +ensures that the dialogue displays a consistent set of results, while not +blocking normal lock manager operations longer than necessary. Nonetheless +there could be some impact on database performance if this view is read often. +

+

+

+
+

+On a PostgreSQL server running version 8.1 or newer, the Transaction tab allows +you to view outstanding prepared transactions. Prepared transactions are an aspect +of Two Phase Commit (2PC), used in distributed transaction managers. Usually, +prepared transactions are handled by the transaction manager. In case of a failure, +it might be necessary to commit or rollback a transaction manually; you can use +the 'Commit' or 'Rollback' buttons to do this. +

+

+

+
+

+The Logfile tab shows server log files, if configured in +postgresql.conf (redirect_stderr = true, +log_destination='stderr' and log_filename='postgresql-%Y-%m-%d_%H%M%S.log'). +pgAdmin will extract a time stamp from the logfile in a separate column, if the +log_line_prefix is configured accordingly. We recommend using '%t:' as +format, because more complicate formats might not be interpretable correctly. +

+

+The combobox allows you to select historic logfiles or the current +one. If "current" is selected, pgAdmin will correctly detect +logfile rotation and continue to display them. +

+

+The "Rotate" button will force the server to rotate its server +logfile. This function is currently not implemented on 8.0 servers; if +you think this is valuable for you please contact us. +

+

+Please note that displaying the logfile requires +additional functions loaded on the server side, which are +available for 8.x servers only. +

+

+To refresh the display click the Refresh button. The display will +also be automatically refreshed based on the refresh interval specified. +

+ + + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/main.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/main.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/main.html (revision 1448) @@ -0,0 +1,66 @@ + + + + + +pgAdmin Main Window + + + + +

pgAdmin Main Window

+ +
+ +

In the main window, the structure of the databases is displayed. +You can create new objects, delete and edit existing objects if the +privileges of the user that you are using on the current connection +to the database allow this.

+

The left side of the main window shows a tree with all servers, +and the objects they contain.

+

The upper right side shows details of the object currently +selected in the tree. Some objects might have statistics in addition +to their properties, these can be shown if you select the Statistics +tab.

+

The lower right side contains a reverse engineered SQL script. You +can copy this to any editor using cut&paste, or save it to a file +using Save definition... from the File menu, or use it as a template +if you select the Query Tool. If the + Copy SQL option is selected, the SQL +query will be copied automatically to the tool.

+

The status line will show you some status information, as well as +the time the last action took pgAdmin III to complete.

+

You can resize the main window, and change the sizes of the three +main regions as you prefer. These adjustments will be preserved when +you exit the program.

+ +

pgAdmin is bandwidth friendly. The status of objects in the browser +is only refreshed on request or after changes made with the built-in tools. +Be aware that this does not cover changes made via manual SQL or from other +users or other clients. It is generally advisable to manually refresh +objects before working on them in such environments.

+ +

Getting started

+

After you have added the desired server(s) to the tree on the left +side using the Add server menu or toolbar +button, each server will show up under the top node "Servers". +

+

To open a connection to a server, select the desired server in the +tree, and double click on it or use Connect from the Tools menu. The +connection will be established, and the properties of the top level +objects are retrieved from the database server. If you've been +connected to that database previously, pgAdmin III will restore the +previous selection of database and schema for you. The current +situation is saved when exiting the program, so that pgAdmin III is +able to restore the previous environment.

+

Using the menu or toolbar buttons, you can create new objects, +delete objects and edit properties of existing objects if the user +that you entered when adding the server connection has sufficient +privileges. You may find some options grayed out if displaying +properties. This means, that the database server you're currently +using doesn't support the feature, or that this property can't be +changed by design, or that your user privileges won't allow you to +change it.

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/macros.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/macros.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/macros.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + Query Tool Macros + + +

+ Query Tool Macros +

+
+ +

+ Query Tool Macros enable you to execute pre-defined SQL queries + with single key press. Pre-defined queries can contain the placeholder + $SELECTION$. Upon macro execution the placeholder will be replaced with + the text current selected in the SQL pane of the Query Tool. +

+ +

To create a macro, select the Manage Macros option from the Macros menu + on the Query Tool. Select the key you wish to use, enter the name of the macro, + and the query, optionally including the selection placeholder, and then click + the Save button to store the macro. +

+ +

To clear a macro, select the macro on the Manage Macros dialogue, and then + click the Clear button. +

+ +

To execute a macro, simply press the appropriate shortcut keys, or select + it from the Macros menu. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/control-server.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/control-server.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/control-server.html (revision 1448) @@ -0,0 +1,20 @@ + + + + + +Control Server + + + + +

Control Server

+

+If you entered correct data in the Server +property dialogue service field, pgAdmin will check if the service is +running, and allows to start and stop the service. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/using.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/using.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/using.html (revision 1448) @@ -0,0 +1,57 @@ + + + + + +Using pgAdmin + + + + +

Using pgAdmin

+

This section explains how you can use pgAdmin to maintain your +PostgreSQL databases. pgAdmin supports database server versions +7.3 and up. Versions older than 7.3 are not supported, please use +pgAdmin II for these.

+ +

When editing the properties of a database object, pgAdmin will +support you with help about the underlying PostgreSQL SQL commands, +if you press the F1 function key. In order for this to work, the sql +helpsite setting in the options dialog +must be set correctly.

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/default-xsl.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/default-xsl.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/default-xsl.html (revision 1448) @@ -0,0 +1,220 @@ + + + + + +Default XSL stylesheet + + + + +

Default XSL stylesheet

+ +

+For reference, and as a starting point for your own stylesheets, the builtin stylesheet +that pgAdmin uses to render XHTML report output from XML report data is included below. +This stylesheet includes the default HTML stylesheet that will be embedded into a report +to give it the pgAdmin look and feel. +

+ +
+<?xml version="1.0"?>
+<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
+<xsl:output method="xml" doctype-system="http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd" doctype-public="-//W3C//DTD XHTML 1.0 Transitional//EN" indent="yes" encoding="utf-8" />
+<xsl:template match="/report">
+
+<html>
+  <head>
+    <xsl:if test="header/title != ''">
+      <title><xsl:value-of select="header/title" /></title>
+    </xsl:if>
+    <meta http-equiv="Content-Type" content="utf-8" />
+    <style type="text/css">
+      body {  font-family: verdana, helvetica, sans-serif; margin: 0px; padding: 0; }
+      h1 { font-weight: bold; font-size: 150%; border-bottom-style: solid; border-bottom-width: 2px; margin-top: 0px; padding-bottom: 0.5ex; color: #eeeeee; }
+      h2 { font-size: 130%; padding-bottom: 0.5ex; color: #009ace; border-bottom-style: solid; border-bottom-width: 2px; }
+      h3 { font-size: 110%; padding-bottom: 0.5ex; color: #000000; }
+      th { text-align: left; background-color: #009ace; color: #eeeeee; }
+      #ReportHeader { padding: 10px; background-color: #009ace; color: #eeeeee; border-bottom-style: solid; border-bottom-width: 2px; border-color: #999999; }
+      #ReportHeader th { width: 25%; white-space: nowrap; vertical-align: top; }
+      #ReportHeader td { vertical-align: top; color: #eeeeee; }
+      #ReportNotes { padding: 10px; background-color: #eeeeee; font-size: 80%; border-bottom-style: solid; border-bottom-width: 2px; border-color: #999999; }
+      .ReportSQL { margin-bottom: 10px; padding: 10px; display: block; background-color: #eeeeee; font-family: monospace; }
+      #ReportDetails { margin-left: 10px; margin-right: 10px; margin-bottom: 10px; }
+      #ReportDetails td, th { font-size: 80%; margin-left: 2px; margin-right: 2px; }
+      #ReportDetails th { border-bottom-color: #777777; border-bottom-style: solid; border-bottom-width: 2px; }
+      .ReportDetailsOddDataRow { background-color: #dddddd; }
+      .ReportDetailsEvenDataRow { background-color: #eeeeee; }
+      .ReportTableHeaderCell { background-color: #dddddd; color: #009ace; vertical-align: top; font-size: 80%; white-space: nowrap; }
+      .ReportTableValueCell { vertical-align: top; font-size: 80%; white-space: nowrap; }
+      .ReportTableInfo { font-size: 80%; font-style: italic; }
+      #ReportFooter { font-weight: bold; font-size: 80%; text-align: right; background-color: #009ace; color: #eeeeee; margin-top: 10px; padding: 2px; border-bottom-style: solid; border-bottom-width: 2px; border-top-style: solid; border-top-width: 2px; border-color: #999999; }
+      #ReportFooter a { color: #ffffff; text-decoration: none; }
+    </style>
+  </head>
+
+  <body>
+    <div id="ReportHeader">
+
+    <xsl:if test="header/title != ''">
+      <h1><xsl:value-of select="header/title" /></h1>
+    </xsl:if>
+
+    <xsl:if test="header/generated != ''">
+      <b>Generated: </b><xsl:value-of select="header/generated" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/server != ''">
+      <b>Server: </b><xsl:value-of select="header/server" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/database != ''">
+      <b>Database: </b><xsl:value-of select="header/database" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/catalog != ''">
+      <b>Catalog: </b><xsl:value-of select="header/catalog" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/schema != ''">
+      <b>Schema: </b><xsl:value-of select="header/schema" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/table != ''">
+      <b>Table: </b><xsl:value-of select="header/table" /><br />
+    </xsl:if>
+
+    <xsl:if test="header/job != ''">
+      <b>Job: </b><xsl:value-of select="header/job" /><br />
+    </xsl:if>
+
+    </div>
+
+    <xsl:if test="header/notes != ''">
+      <div id="ReportNotes">
+      <b>Notes: </b><br /><br />
+      <xsl:call-template name="substitute">
+         <xsl:with-param name="string" select="header/notes" />
+      </xsl:call-template>
+      </div>
+    </xsl:if>
+
+    <div id="ReportDetails">
+      <xsl:apply-templates select="section" >
+        <xsl:sort select="@number" data-type="number" order="ascending" />
+      </xsl:apply-templates>
+    </div>
+
+    <div id="ReportFooter">
+Report generated by <a href="http://www.pgadmin.org/">pgAdmin</a>
+    </div>
+
+    <br />
+  </body>
+</html>
+
+</xsl:template>
+
+<xsl:template match="section">
+  <xsl:if test="../section[@id = current()/@id]/@name != ''">
+    <h2><xsl:value-of select="../section[@id = current()/@id]/@name" /></h2>
+  </xsl:if>
+
+  <xsl:if test="count(../section[@id = current()/@id]/table/columns/column) > 0">
+    <table>
+      <tr>
+        <xsl:apply-templates select="../section[@id = current()/@id]/table/columns/column">
+          <xsl:sort select="@number" data-type="number" order="ascending" />
+          <xsl:with-param name="count" select="count(../section[@id = current()/@id]/table/columns/column)" />
+        </xsl:apply-templates>
+      </tr>
+      <xsl:apply-templates select="../section[@id = current()/@id]/table/rows/*" mode="rows">
+          <xsl:sort select="@number" data-type="number" order="ascending" />
+        <xsl:with-param name="column-meta" select="../section[@id = current()/@id]/table/columns/column" />
+      </xsl:apply-templates>
+    </table>
+    <br />
+    <xsl:if test="../section[@id = current()/@id]/table/info != ''">
+      <p class="ReportTableInfo"><xsl:value-of select="../section[@id = current()/@id]/table/info" /></p>
+    </xsl:if>
+  </xsl:if>
+
+  <xsl:if test="../section[@id = current()/@id]/sql != ''">
+    <pre class="ReportSQL">
+      <xsl:call-template name="substitute">
+         <xsl:with-param name="string" select="../section[@id = current()/@id]/sql" />
+      </xsl:call-template>
+    </pre>
+  </xsl:if>
+</xsl:template>
+
+<xsl:template match="column">
+  <xsl:param name="count" />
+  <th class="ReportTableHeaderCell">
+  <xsl:attribute name="width"><xsl:value-of select="100 div $count" />%</xsl:attribute>
+    <xsl:call-template name="substitute">
+       <xsl:with-param name="string" select="@name" />
+    </xsl:call-template>
+  </th>
+</xsl:template>
+
+<xsl:template match="*" mode="rows">
+  <xsl:param name="column-meta" />
+  <tr>
+  <xsl:choose>
+  <xsl:when test="position() mod 2 != 1">
+    <xsl:attribute name="class">ReportDetailsOddDataRow</xsl:attribute>
+  </xsl:when>
+  <xsl:otherwise>
+    <xsl:attribute name="class">ReportDetailsEvenDataRow</xsl:attribute>
+  </xsl:otherwise>
+  </xsl:choose>
+    <xsl:apply-templates select="$column-meta" mode="cells">
+      <xsl:with-param name="row" select="." />
+    </xsl:apply-templates>
+  </tr>
+</xsl:template>
+
+<xsl:template match="*" mode="cells">
+  <xsl:param name="row" />
+    <td class="ReportTableValueCell">
+    <xsl:choose>
+      <xsl:when test="$row/@*[name() = current()/@id]|$row/*[name() = current()/@id] != ''">
+        <xsl:call-template name="substitute">
+          <xsl:with-param name="string" select="$row/@*[name() = current()/@id]|$row/*[name() = current()/@id]" />
+        </xsl:call-template>
+      </xsl:when>
+      <xsl:otherwise>
+        <xsl:text> </xsl:text>
+      </xsl:otherwise>
+    </xsl:choose>
+  </td>
+</xsl:template>
+
+<xsl:template name="substitute">
+   <xsl:param name="string" />
+   <xsl:param name="from" select="'&#xA;'" />
+   <xsl:param name="to">
+      <br />
+   </xsl:param>
+   <xsl:choose>
+      <xsl:when test="contains($string, $from)">
+         <xsl:value-of select="substring-before($string, $from)" />
+         <xsl:copy-of select="$to" />
+         <xsl:call-template name="substitute">
+            <xsl:with-param name="string" select="substring-after($string, $from)" />
+            <xsl:with-param name="from" select="$from" />
+            <xsl:with-param name="to" select="$to" />
+         </xsl:call-template>
+      </xsl:when>
+      <xsl:otherwise>
+         <xsl:value-of select="$string" />
+      </xsl:otherwise>
+   </xsl:choose>
+</xsl:template>
+
+</xsl:stylesheet>
+
+
+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +PostgreSQL's performance can be improved by VACUUMing your databases regularly. +PostgreSQL's official birthday is the 8th of July. The PostgreSQL project was born in 1996. +The first prototype for the original pgAdmin project was called pgManager and was written for PostgreSQL 6.3.2. +Support for pgAdmin can be requested through the pgadmin-support@postgresql.org mailing list. +New features and developments are discussed by the pgAdmin Developers through the pgadmin-hackers@postgresql.org mailing list. +The majority of the pgSchema library used by pgAdmin II was developed on a Windows 2000 laptop in front of a TV near Oxford, England! +You can change your password by selecting 'Change Password' from the 'File' menu. +The Definition Pane displays the reversed engineered SQL for the selected object. +The answer to the question of Life, the Universe and Everything is 42. +The pgAdmin core developers are based in the UK, France, Germany, Italy and the US. +PostgreSQL 7.2 and up supports tables without OID columns in order to cut down on OID usage. +You can monitor system activity on a per connection basis using the Status tool. +There are a number of useful files, tools and projects included with PostgreSQL in the /contrib directory of the source tree. +PostgreSQL's procedural languages include pl/pgSQL, pl/Python, pl/TCL, pl/Perl & pl/sh. +pgAdmin II was downloaded over 10,000 times *before* the first release quality version was available! +The first stable version of pgAdmin II was downloaded over 35,000 times in the first 6 months following it's release. +The Slony-I project from www.slony.info can be used for Master -> Slave replication. +The first official stable version of pgAdmin II was released on 16 January 2002. +Development of the pgAdmin III project started on the 29th September 2002. +pgAdmin III is a completely new version of pgAdmin written in C++ using the wxWidgets framework to allow it to run on Windows and *nix systems. +pgAdmin is released under the Open Source 'Artistic Licence'. +PostgreSQL 7.3 supports schemas which are individual namespaces within databases. +Domains may be used to create predefined data types based on more generic base types. +pgAdmin III 1.0.0 was packaged for release on the 26th September 2003. +PostgreSQL's planner will ignore your desire to choose an index scan if your joining column's datatypes do not match. +You shouldn't 'kill -9' the postmaster!! +'EXPLAIN ANALYZE' and the 'Explain Query' button are your friends when optimising SQL queries. +PostgreSQL 8.0 added major new features to our DBMS including savepoints, tablespaces and the long awaited Windows port. +pgAdmin III supports SSL encrypted connections. +The new Win32 port PostgreSQL passed all it's regression tests for the first time on 2004-10-24. +The Windows port of PostgreSQL was downloaded over 45,000 times in the five days following its initial release! +The bug "Don't enable the OK button when setting the ACL for as-yet-uncreated objects" was fixed at 39,000 feet over Finland whilst Andreas, Magnus and Dave returned from Slony-I and pgAdmin III presentation in Japan! +Configuring PostgreSQL with too many shared buffers can have a detrimental effect on performance because it reduces the amount of RAM available for the operating system kernel to use as filesystem cache. +Sitting on a plane for 12 hours is really mind numbingly boring which is why I'm writing new tips right now!! +The Japan PostgreSQL Users Group or JPUG has over 5000 members and is growing all the time. +pgAdmin 1.4 is supported on more platforms than any previous version, including numerous Linux distributions, Microsoft Windows (tm), FreeBSD, Solaris and Mac OS X. +pgAdmin 1.4 includes a graphical EXPLAIN tool to allow you to more easily read and understand query plans. +pgAgent can be used to schedule regular batch and SQL jobs, such as the re-creation of date-sensitive partial indexes, or purging of old records. +It is good practice to build application logic into the database itself by using functions and views. This ensures that different front-ends to your products will always see the same views of data and update and modify data in the same way. Better yet, you only have to write it all once for all front-ends! +To help keep your databases secure, minimise the amount of access you allow to remote hosts when creating your pg_hba.conf file, and always use encrypted connections unless you have good reason not to. +You can restrict access to individual columns of a table for a particular user or group by denying them direct access to it, and creating a view containing only the columns they should see for them to use instead. If your users need to update the data, you can create rules to apply updates to the view to the base table instead. +PostgreSQL has been run on diverse platforms such as the Microsoft X Box, Sony PlayStation II, and Sharp Zaurus PDAs! +EnterpriseDB donated an Apple Powerbook to the pgAdmin project to help improve the Mac OS X port of pgAdmin and their simplified derivative product, EDB Studio. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/editgrid.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/editgrid.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/editgrid.html (revision 1448) @@ -0,0 +1,54 @@ + + + + + +Edit Data + + + + +

Edit Grid

+ +
+ +

The Edit Grid tool allows you to view the data that's stored in a +table or view, and to edit the content if technically possible.

+

The header of the grid will show the name of each column, together +with the data type. A column that's part of the primary key will +additionally be marked with [PK].

+

Important: In order to edit the data, each row in the table must be uniquely +identifiable. This can be done using the OID, or a primary key. If +none of them exist, the table is read only. Note that views can't be +edited and are read only by design; updatable views (using rules) are +not supported at this time.

+

To change the value of a field, you select that field and enter +the new text. The Store toolbar button allows the data to be written +back to the server. The row will be written automatically, if you +select a different row.

+

To enter a new row into the table, you enter the data into the +last row that has a row number marked with an asterisk. As soon as +you store the data, the row will get a row number, and a fresh empty +asterisk line is created.

+

If an SQL NULL is to be written to the table, simply leave the field +empty. If you store a new row, this will let the server fill in the +default value for that column. If you store a change to an existing +row, the value NULL will explicitly be written.

+

To enter a newline into a field, press Ctrl-Enter.

+

If you want pgAdmin III to write an empty string to the table, you +enter the special string '' (two single quotes) in the field. If you +want to write a string containing solely two single quotes to the +table, you need to escape these quotes, by typing \'\' +

+

To delete a row, press the Delete toolbar button.

+

The Refresh toolbar button allows to reread the contents of the +table, refreshing the display.

+

+You can select one or more rows, and copy them with Ctrl-C or the Copy +toolbar button to the clipboard. +

+The Sort/Filter toolbar button will open the View Data Options dialog. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/gridopts.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/gridopts.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/gridopts.html (revision 1448) @@ -0,0 +1,34 @@ + + + + + +View Data Options + + + + +

View Data Options

+ +

When "Apply Filter and View Data" is selected from the main menu, +or the "Sort/Filter" toolbar button is pressed in the data viewer, +this dialogue appears. It allows changing the sort order of the data, +and applying a filter to narrow the displayed data. +

+

+

+

+

+You can select one or more columns and the sort direction which should +be used to retrieve the data from the database. +

+

+

+
+

+You can enter an arbitrary WHERE clause, to restrict the result set +which is retrieved from the database. You can click "Validate" to have +pgAdmin III test whether the WHERE clause is valid. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-example.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-example.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-example.html (revision 1448) @@ -0,0 +1,159 @@ + + + + + +Slony-I example + + + + +

Slony-I example

+ +

+In this example, a master server is setup with two direct slaves. This example was +written and tested using Slony-I v1.2.11 and PostgreSQL 8.2.5, running on a single +Windows XP machine. The PostgresSQL pgbench utility is used to generate the test +schema and workload. +

+ +

    +
  1. Create 3 databases, master, slave1 and slave2 and ensure pl/pgsql is setup + in each.
     
    2. + +
  2. Create a pgbench schema in the master database:

    + + > pgbench -i -U postgres master
     
    3. + +
  3. Add a primary key called history_pkey to the history table on the tid, bid + and aid columns.
     
    4. + +
  4. Create a schema-only dump of the master database, and load it into slave1 + and slave2:

    + + + > pg_dump -s -U postgres master > schema.sql
    + > psql -U postgres slave1 < schema.sql
    + > psql -U postgres slave2 < schema.sql +
     
    5. + +
  5. Create Slony config files for each slon engine (daemon on *nix). The files + should contain just the following two lines:

    + + + cluster_name='pgbench'
    + conn_info='host=127.0.0.1 port=5432 user=postgres dbname=master' +

    + + Create a file for each database, adjusting the dbname parameter as + required and adding any other connection options that may be + needed.
     
    6. + +
  6. (Windows only) Install the Slony-I service:

    + + + > slon -regservice Slony-I +
     
    7. + +
  7. Register each of the engines (this is only necessary on Windows - on *nix + the slon daemons may be started individually and given the path to the + config file on the command line using the -f option):

    + + + > slon -addengine Slony-I C:\slony\master.conf
    + > slon -addengine Slony-I C:\slony\slave1.conf
    + > slon -addengine Slony-I C:\slony\slave2.conf +
     
    8. + +
  8. In pgAdmin under the Replication node in the master database, create a new + Slony-I cluster using the following options:

    + + 
    +Join existing cluster: Unchecked
+Cluster name:          pgbench
+Local node:            1        Master node
+Admin node:            99       Admin node
+
    9. + +
  9. Under the Replication node, create a Slony-I cluster in each of the slave + databases using the following options:

    + + 
    +Join existing cluster: Checked
+Server:                <Select the server containing the master database>
+Database:              master
+Cluster name:          pgbench
+Local node:            10       Slave node 1
+Admin node:            99 - Admin node
+
+Join existing cluster: Checked
+Server:                <Select the server containing the master database>
+Database:              master
+Cluster name:          pgbench
+Local node:            20       Slave node 2
+Admin node:            99 - Admin node
+
    10. + +
  10. Create Paths on the master to both slaves, and on each slave back to the + master. Create the paths under each node on the master, using the + connection strings specified in the slon config files. Note that future + restructuring of the cluster may require additional paths to be defined. +
     
    11. + +
  11. Create a Replication Set on the master using the following settings: +

    + + 
    +ID:                  1
+Comment:             pgbench set
+
    12. + +
  12. Add the tables to the replication set using the following settings: +

    + + 
    +Table:               public.accounts
+ID:                  1
+Index:               accounts_pkey
+
+Table:               public.branches
+ID:                  2
+Index:               branches_pkey
+
+Table:               public.history
+ID:                  3
+Index:               history_pkey
+
+Table:               public.tellers
+ID:                  4
+Index:               tellers_pkey
+
    13. + +
  13. On the master node, create a new subscription for each slave using the + following options:

    + + 
    +Origin:              1
+Provider:            1 - Master node
+Receiver:            10 - Slave node 1
+
+Origin:              1
+Provider:            1 - Master node
+Receiver:            20 - Slave node 2
+
    14. + +
  14. Start the slon service (or daemons on *nix):

    + + + > net start Slony-I +
     
    15. +
+ +

+Initial replication should begin and can be monitored on the statistics tab in +pgAdmin for each node. The pgbench utility may be run against the master +database to generate a test workload. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-path.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-path.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-path.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Creating paths and listens + + + +

Creating paths and listens

+ + +

Create paths to other nodes

+
+
+

+Slony-I needs path information, that defines how a slon process can communicate to +other nodes. The conninfo string takes a connect string as described in the +libpq connection documentation. +Usually, you will need to specify host, dbname and username, while the password should +be stored in the .pgpass file. +

+ +

+You must create a path to every other node, on each node. For example, in a two node cluster +you need to create a path to the slave on the master, and one to the master on the slave. +

+ + +

Create listens to other nodes

+
+
+

+After the communication path has been defined, the slon processes need to be +advised to listen to events from other nodes. +

+ +

+Note: This step is not necessary for Slony-I v1.1 +and later, because listen information is generated automatically when paths are defined. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-schedules.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-schedules.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-schedules.html (revision 1448) @@ -0,0 +1,54 @@ + + + + + +pgAgent Schedules + + + + +

pgAgent Schedules

+

Each Job is executed according to one or more schedules. Each time the +job or any or any of it's schedules are altered, the next runtime of the +job is re-calculated. Each instance of pgAgent periodically polls the database +for jobs with the next runtime value in the past. By polling at least once +every minute, all jobs will normally start within one minute of the specified +start time. If no pgAgent instance is running at the next runtime of a job, +it will run as soon as pgAgent is next started, folliwng which it will return to +the normal schedule.

+ +

Schedules may be added to a job through the job properties dialogue, or added +as a sub-object. The Properties tab of the main pgAdmin window will display +details of the selected schedule.

+ +

Schedule properties

+ +

Each schedule consists of the basic details such as a name, whether or not it +is enable and a comment. In addition, a start date and time is specified (before +which the schedule has no effect), and optionally and end date and time (after +which the schedule has no effect).

+ +

Step details - properties tab

+ +

Schedules are specified using a cron-style format, For each selected time or +date element, the schedule will execute. For example, to execute at 5 minutes +past every hour, simply tick '5' in the Minutes list box. Values from more than +one field may be specified in order to further control the schedule. For example, +to execute at 12:05 and 14:05 every Monday and Thursday, you would tick minute 5, +hours 12 and 14, and weekdays Monday and Thursday. For additional flexibility, +the Month Days check list includes an extra Last Day option. This matches the +last day of the month, whether it happens to be the 28th, 29th, 30th or 31st.

+ +

Step details - days & times tabs

+ +

On occasion it may be desirable to specify an exception for a schedule - for +example, you may not want a schedule to fire on a particular national holiday. +To achieve this, each schedule may have a list of dates and or time exceptions +attached to it. If an schedule lands on an exception, that instance will be +skipped, and the following occurance will become the next runtime.

+ +

Step details - exceptions tab

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/licence.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/licence.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/licence.html (revision 1448) @@ -0,0 +1,124 @@ + + + + + +The Artistic Licence + + + +

BY INSTALLING OR DISTRIBUTING PGADMIN AND RELATED SOFTWARE, YOU AGREE WITH +THE FOLLOWING DISCLAIMER:

+ +

PGADMIN AND RELATED SOFTWARE IS PROVIDED WITHOUT GUARANTEE OR WARRANTY OF +ANY KIND. TO THE FULLEST EXTENT ALLOWED BY LAW YOU AGREE THAT THE PGADMIN +DEVELOPMENT TEAM MEMBERS, CONTRIBUTERS OR DISTRIBUTORS OF THE SOFTWARE CANNOT +AND WILL NOT BE HELD LIABLE FOR ANY DIRECT OR INDIRECT DAMAGE OR LOSSES CAUSED +WHOLLY OR IN PART BY THE SOFTWARE.

+ +

IN COUNTRIES WHERE THE ABSENCE OF LIABILITY MAY NOT EXIST OR BE RESTRICTED +BY LAW, PGADMIN DEVELOPMENT TEAM MEMBERS, CONTRIBUTORS AND DISTRIBUTORS +LIABILITY SHALL BE LIMITED TO ONE EURO.

+ +

The Artistic Licence

+

Preamble

+

The intent of this document is to state the conditions under which +a Package may be copied, such that the Copyright Holder maintains +some semblance of artistic control over the development of the +package, while giving the users of the package the right to use and +distribute the Package in a more-or-less customary fashion, plus the +right to make reasonable modifications.

+

Definitions:

+ +

1. You may make and give away verbatim copies of the source form +of the Standard Version of this Package without restriction, provided +that you duplicate all of the original copyright notices and +associated disclaimers.

+

2. You may apply bug fixes, portability fixes and other +modifications derived from the Public Domain or from the Copyright +Holder. A Package modified in such a way shall still be considered +the Standard Version.

+

3. You may otherwise modify your copy of this Package in any way, +provided that you insert a prominent notice in each changed file +stating how and when you changed that file, and provided that you do +at least ONE of the following:

+
a) place your modifications in the Public Domain or +otherwise make them Freely Available, such as by posting said +modifications to Usenet or an equivalent medium, or placing the +modifications on a major archive site such as ftp.uu.net, or by +allowing the Copyright Holder to include your modifications in the +Standard Version of the Package.
+
b) use the modified Package only within your corporation +or organization.
+
c) rename any non-standard executables so the names do +not conflict with standard executables, which must also be provided, +and provide a separate manual page for each non-standard executable +that clearly documents how it differs from the Standard Version.
+
d) make other distribution arrangements with the +Copyright Holder.
+

4. You may distribute the programs of this Package in object code +or executable form, provided that you do at least ONE of the +following:

+
a) distribute a Standard Version of the executables and +library files, together with instructions (in the manual page or +equivalent) on where to get the Standard Version.
+
b) accompany the distribution with the machine-readable +source of the Package with your modifications.
+
c) accompany any non-standard executables with their +corresponding Standard Version executables, giving the non-standard +executables non-standard names, and clearly documenting the +differences in manual pages (or equivalent), together with +instructions on where to get the Standard Version.
+
d) make other distribution arrangements with the +Copyright Holder.
+

5. You may charge a reasonable copying fee for any distribution of +this Package. You may charge any fee you choose for support of this +Package. You may not charge a fee for this Package itself. However, +you may distribute this Package in aggregate with other (possibly +commercial) programs as part of a larger (possibly commercial) +software distribution provided that you do not advertise this Package +as a product of your own.

+

6. The scripts and library files supplied as input to or produced +as output from the programs of this Package do not automatically fall +under the copyright of this Package, but belong to whomever generated +them, and may be sold commercially, and may be aggregated with this +Package.

+

7. C or perl subroutines supplied by you and linked into this +Package shall not be considered part of this Package.

+

8. The name of the Copyright Holder may not be used to endorse or +promote products derived from this software without specific prior +written permission.

+

9. THIS PACKAGE IS PROVIDED "AS IS" AND WITHOUT ANY +EXPRESS OR IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE +IMPLIED WARRANTIES OF MERCHANTIBILITY AND FITNESS FOR A PARTICULAR +PURPOSE.

+

The End

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/password.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/password.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/password.html (revision 1448) @@ -0,0 +1,47 @@ + + + + + +Change Password + + + + +

Change Password

+
Change Password Dialogue
+ +

+To change your password, follow the following steps: +

+ +
    +
  1. Enter your current password in the Current Password textbox.
     
    2. +
  2. Enter your desired password in the New Password textbox.
     
    3. +
  3. Enter your desired password again, this time in the Confirm Password textbox.
     
    4. +
  4. Click the OK button. +
+ +

Good Practice

+

+It is good policy to set a password to protect your data, even in 'safe' environments such as at home. In +the workplace, failure to apply an appropriate password policy could leave you in breach of Data Protection +laws in some circumstances. +

+ +

+pgAdmin does not enforce any password restrictions, however we do recommend that you consider the following +guidelines when selecting passwords. This is not an exhaustive list and will not guarantee security. +

+ + + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony.html (revision 1448) @@ -0,0 +1,38 @@ + + + + + +Slony-I support + + + + +

Slony-I support

+

pgAdmin III includes a frontend to Slony-I, the most popular master-slave +replication solution for PostgreSQL. pgAdmin III makes maintaining the replication +setup easier, and features health information to monitor the state of the cluster.

+ + +
+

+For further information, please refer to the official Slony-I documentation +which is embedded in this help. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/query.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/query.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/query.html (revision 1448) @@ -0,0 +1,122 @@ + + + + + +Query Tool + + + + +

Query Tool

+ +
+ +

The Query Tool enables you to execute arbitrary SQL commands. All +rules that are mentioned in the PostgreSQL User's guide apply. +

+

The upper part of the Query Tool contains the edit entry window, +where you type your commands. You may read the query from a file, or +write it out to a file. When writing a file, the encoding of the file +is determined by the file suffix: if it is *.sql, a 8 byte local +character set is used. If *.usql is selected, the file will be +written in UTF-8, which enables the storage of virtually all +characters used throughout the world, according to the coding rules +of the Unicode Consortium. If +you select *.*, the setting from the read/write +unicode option is used.

+ +

The edit entry window also contains autocompletion code to help you +write queries. To use autocomplete, simply start typing your query +and then press Control+Space to see a list of possible object names to +insert. For example, type "SELECT * FROM " (without the quotes, but +with the trailing space), and then hit Control and Space together to see +a popup menu of autocomplete options. The autocomplete system is based on +code from psql, the PostgreSQL command line interpreter and will +generally be able to offer autocomplete options in the same places that +it can in psql. You can optionally enable the Tab key to activate +the autocomplete feature as well - the can be done on the +options dialog.

+ +

To execute the query, you select Execute from the Query menu, or +you press the execute toolbar button, or you press the F5 function +key. If you didn't select a word, the complete contents of the window +will be sent to the database server, which executes it. You may also +execute just a part of the text, by selecting only the text that you +want the server to execute.

+

Explain from the Query menu, or F7 function key will execute the +EXPLAIN command. The database server will analyze the query that's +sent to it, and will return the results. +

+

+

+The result is displayed as text in the Data Output page, and graphically +visualized on the Explain page. This enables you to find out how the query is parsed, optimized and executed. You can modify the +degree of inspection by changing the Explain options for this in the +Query menu. Please note that "EXPLAIN VERBOSE" can not be displayed graphically.

+

In case the query you sent to the server using the Execute or +Explain command takes longer than you expect, and you would like to +abort the execution, you can select Cancel from the Query menu, press +the Cancel toolbar button or use Alt-Break function key to abort the +execution. +

+

If you want to have help about a SQL command you want to execute, +you can mark a SQL keyword and select SQL Help from the Help menu, +the SQL Help toolbar button or simply press the F1 key. pgAdmin III +will try to locate the appropriate information in the PostgreSQL +documentation for you.

+

The result of the database server execution will be displayed in +the lower part of the Query Tool. If the last command in the chain of +SQL command sent to the server was as command returning a result set, +this will be shown on the Data Output page. All rowsets from previous +commands will be discarded.

+

To save the data in the Data Output page to a file, you can use +the Export dialog. +

+

Information about all commands just executed will go to the +Messages page. The History page will remember all commands executed +and the results from this, until you use Clear History from the Query +menu to clear the window. If you want to retain the history for later +inspection, you can save the contents of the History page to a file +using the Save history option from the Query menu.

+

The status line will show how long the last query took to +complete. If a dataset was returned, not only the elapsed time for +server execution is displayed, but also the time to retrieve the data +from the server to the Data Output page.

+

+In the toolbar combobox you can quickly change your database connection from +one database to another, without launching another instance of the query tool. +Initially, only one database will be available, but by selecting &less;new connection> from +the combobox, you can add another connection to it. +

+

+

+

In the options dialog, you +can specify a default limit for the rowset size to retrieve. By +default, this value will be 100. If the number of rows to retrieve +from the server exceeds this value, a message box will appear asking +what to do to prevent retrieval of an unexpected high amount of data. +You may decide to retrieve just the first rows, as configured with +tha max rows setting, or retrieving the complete rowset regardless of +the setting, or abort the query, effectively retrieving zero rows.

+ +

If you have queries that you execute often, you can add these to the +favourites menu, and have them automatically put in the buffer when you +select them from the menu. The Manage Favoutites menu option may be used +to organise your favourites. Alternatively, you can store them as +Macros

+ +

The Query Tool also includes a powerful Find and Replace tool. In addition +to offering the normal options found in most tools, a Regular Expression search +mode is included which allows you to perform extremely powerful search +(and replace) operations. Unless your copy of pgAdmin was built against a +non-standard build of wxWidgets, a built in version of Henry Spencer's regular +expression library is used based on the 1003.2 spec and some (not quite all) of the +Perl5 extensions.

+ +

For more details of the regular expression syntax offered, please see the +wxWidgets +documentation.

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/grantwiz.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/grantwiz.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/grantwiz.html (revision 1448) @@ -0,0 +1,34 @@ + + + + + +Grant Wizard + + + + +

Grant Wizard

+ +
+ +

+The Grant Wizard allows assignment of a set of privileges to groups and users to +multiple objects (tables, sequences, views and functions) in a convenient way. +

+

+The Selection tab will show all applicable objects under the currently selected object. +Check all objects you like to grant privileges on. +

+The security tab defines the privileges and groups/users that should be granted. Assigning +no privileges to a group or user will result in revoking all rights for them. +

+

+The SQL tab shows the sql commands that are generated from the selected grant targets. +

+

+When clicking OK, the sql commands will be executed; any result will be displayed in the +Messages tab. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-install.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-install.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-install.html (revision 1448) @@ -0,0 +1,93 @@ + + + + + +Slony-I administration with pgAdmin III: installation + + + + +

Slony-I administration with pgAdmin III: installation

+
+

Prerequisites

+

+As a prerequisite to running Slony-I on PostgreSQL, the slony modules +xxid and slony1_funcs must be present on all servers that have are to run a +Slony-I replication node. This is usually done by the Slony-I installation routine. +

+ + +

Overview

+

+Setting up Slony-I for the first time can be a daunting task. The following sections of +the pgAdmin helpfile will help guide you through creation of your first cluster. +

+

+

+Note: At this point, the slon daemons (service engines on Windows) should be started. +

+
+ + +

Create cluster and first node

+
+
+ +

+To install a Slony-I cluster on the first database, the "New Slony-I Cluster" dialog is +used. It executes the official Slony-I cluster creation SQL scripts, which are located in the +directory configured in the options dialog. +

+

+pgAdmin III needs to store information how to contact each individual node in the cluster. +To achieve this, pgAdmin III uses the concept of "Administrative nodes". + +

+ + +

Join additional nodes to cluster

+
+
+

+After the first node in the Slony-I replication cluster has been successfully created, +all subsequent nodes take their configuration and procedures from the first nodes. +This process is called "Joining a cluster" in pgAdmin III. Usually, you should also select +an existing node as admin node, to insure later accessibility from pgAdmin III. +

+

+After you added a new node to the Slony-I cluster, you need to set up +replication paths between the nodes, to enable communication +between the nodes. +

+ + +

Upgrade node to new cluster software

+
+
+

+When a cluster is to be upgraded to a new version of the Slony-I clustering software, +the upgrade process has to be run on all nodes of the cluster. For each node, the slon +daemon needs to be stopped, then the upgrade dialog is started and a node with +the new software is selected (pgAdmin III will extract all software from that node), +and finally the slon daemon is started again. +

+

+Currently, pgAdmin III does not support upgrading from slony creation scripts. +Instead, create an intermediate cluster from the creation scripts, use it as a source +for the upgrade dialog, and drop the cluster after usage. You may also use the slonik +tool to upgrade the first node, and then use it as source for subsequent node upgrades. +

+

+

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-functions.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-functions.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-functions.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Slony-I tasks + + + +

Slony-I tasks

+

+In the appropriate context, pgAdmin III can trigger several maintenance tasks. +

+

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/kerberos.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/kerberos.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/kerberos.html (revision 1448) @@ -0,0 +1,47 @@ + + + + + +The MIT Kerberos Licence + + + +

pgAdmin PostgreSQL's libpq library which may be linked with MIT Kerberos +Libraries on some distributions. The MIT Kerberos licence is included below:

+ +

Kerberos Copyright

+ +

This software is being provided to you, the LICENSEE, by the Massachusetts +Institute of Technology (M.I.T.) under the following license. By obtaining, using +and/or copying this software, you agree that you have read, understood, and will +comply with these terms and conditions:

+ +

Permission to use, copy, modify and distribute this software and its documentation +for any purpose and without fee or royalty is hereby granted, provided that you +agree to comply with the following copyright notice and statements, including +the disclaimer, and that the same appear on ALL copies of the software and +documentation, including modifications that you make for internal use or for +distribution:

+ +

Copyright 1992-2004 by the Massachusetts Institute of Technology. All rights reserved.

+ +

THIS SOFTWARE IS PROVIDED "AS IS", AND M.I.T. MAKES NO REPRESENTATIONS OR +WARRANTIES, EXPRESS OR IMPLIED. By way of example, but not limitation, M.I.T. +MAKES NO REPRESENTATIONS OR WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY +PARTICULAR PURPOSE OR THAT THE USE OF THE LICENSED SOFTWARE OR DOCUMENTATION +WILL NOT INFRINGE ANY THIRD PARTY PATENTS, COPYRIGHTS, TRADEMARKS OR OTHER +RIGHTS.

+ +

The name of the Massachusetts Institute of Technology or M.I.T. may NOT be used +in advertising or publicity pertaining to distribution of the software. Title to +copyright in this software and any associated documentation shall at all times +remain with M.I.T., and USER agrees to preserve same.

+ +

Project Athena, Athena, Athena MUSE, Discuss, Hesiod, Kerberos, Moira, OLC, +X Window System, and Zephyr are trademarks of the Massachusetts Institute of +Technology (MIT). No commercial use of these trademarks may be made without +prior written permission of MIT.

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-jobs.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-jobs.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-jobs.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +pgAgent Jobs + + + + +

pgAgent Jobs

+

pgAgent runs 'jobs', each of which consists of +steps and +schedules. To configure jobs on your +server, browse to the server on which the pgAgent database objects +were created. A Jobs node will be displayed, under +which individual jobs are shown. New jobs may be created, and existing +jobs modified in the same way as any other object in pgAdmin.

+ +

Job details

+ +

The properties tab in the main pgAdmin window will display the +details of the selected job, and the Statistics tab will show the +details of each run of the job.

+ +

Job statistics

+ +

Job themselves are very simple - the complexity is in the steps and +schedules. When configuring a job, we specify the job name, whether or +not it is enabled, a job class or category, and optionally the hostname +of a specific machine running pgAgent, if this job should only run on +that specific server. If left empty, any server may run the job. This +is not normally an issue for SQL-only jobs, however any jobs with +batch/shell steps may need to be targetted to a specific server. A +comment may also be included.

+ +

Job properties

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect-error.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect-error.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect-error.html (revision 1448) @@ -0,0 +1,66 @@ + + + + + +Connection errors + + + + +

Connect errors

+ +

+When connecting to a PostgreSQL server, you might get error messages that need +some more explanations. If you encounter them, please read the following information +carefully, we're sure they will help you. +
+

+
+

+

could not connect to Server: Connection refused

+
+

+If this message appears, there are two possible reasons for this: either the server isn't +running at all. Simply start it. +

+

+The other non-trivial cause for this message is that the server isn't configured +to accept TCP/IP requests on the address shown. +

+

+For security reasons, a PostgreSQL server "out of the box" doesn't listen on TCP/IP ports. +Instead, it has to be enabled to listen for TCP/IP requests. This can be done by +adding tcpip = true to the postgresql.conf file for Versions 7.3.x and 7.4.x, or +listen_addresses='*' for Version 8.0.x and above; this will make the server +accept connections on any IP interface. +

+

+For further information, please refer to the PostgreSQL documentation about +runtime configuration.
+

+
+

FATAL: no pg_hba.conf entry

+
+

+If this message appears, your server can be contacted correctly over the network, +but isn't configured to accept your connection. Your client isn't detected +as a legal user for the database. +

+

+You will have to add an entry in the form +
   host template1 postgres 192.168.0.0/24 md5 +
for IPV4 or +
   host template1 postgres ::ffff:192.168.0.0/120 md5 +
for IPV6 networks to the +pg_hba.conf file. +

+

+For further information, please refer to the PostgreSQL documentation about +client authentication.
+

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab1.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab1.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab1.html (revision 1448) @@ -0,0 +1,63 @@ + + + + + +pgAdmin Options - Tab 1 (General) + + + + +

pgAdmin Options - Tab 1 (General)

+ +
+ +

+

+

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-steps.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-steps.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-steps.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +pgAgent Steps + + + + +

pgAgent Steps

+

Each Job consists of a number of steps, each of which may be an SQL script, +or an operating system batch/shell script. Each step in a given job is run in +turn, in alphanumeric name order.

+ +

Steps may be added to a job through the job properties dialogue, or added +as a sub-object. The Properties tab of the main pgAdmin window will display +details of the selected step, and the Statistics tab will display details +of each run of the step, including and output or errors from the script.

+ +

Step statistics

+ +

Each step consists of the details shown on the screenshot below, most of +which are self-explanatory. If Kind is set to SQL, then it goes without +saying that a database against which to run the script must be selected. If +set to Batch, the database should be left blank. The On Error option +controls how failure of this step will affect the +status of the overall job.

+ +

Step details

+ +

The Definition tab contains a single text box into which the step +script should be entered. For SQL steps, this should be a series of one or more +SQL statements. For batch jobs, when running on a Windows server, standard +batch file syntax must be used, and when running on a *nix server, any shell +script may be used, provided that a suitable interpreter is specified on the +first line (e.g. #!/bin/sh).

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab3.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab3.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab3.html (revision 1448) @@ -0,0 +1,71 @@ + + + + + +pgAdmin Options - Tab 3 (Query) + + + + +

pgAdmin Options - Tab 3 (Query)

+ +
+ +

+

+

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/maintenance.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/maintenance.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/maintenance.html (revision 1448) @@ -0,0 +1,50 @@ + + + + + +Maintain a database object + + + + +

Maintain a database object

+ +
+ +

This tool allows to maintain the database in total, or only a +selected table, or a selected index.

+

Maintenance comes in three flavors:

+

VACUUM

+

VACUUM will scan the database or table for rows, that are not in +use any more. If a row is updated or deleted, the previous content +isn't replaced, but rather marked invalid. The new data is inserted +freshly into the database. You need to perform a garbage collection +regularly, to insure that your database doesn't contain too much +unused data, wasting disk space and ultimatively degrading +performance.

+

Please press the Help button to see the PostgreSQL help about the +VACUUM command to learn more about the options.

+

The output of the database server is displayed in the messages +page as they arrive. If Verbose is selected, the server will send +very detailed info about what it did.

+

While this tools is very handy for ad-hoc maintenance purposes, +you are encouraged to install an automatic job, that performs a +VACUUM job regularly to keep your database in a neat state.

+

ANALYZE

+

ANALYZE investigates statistical values about the selected +database or table. This enables the query optimizer to select the +fastest query plan, to give optimal performance. Every time your data +is changing radically, you should perform this task. It can be +included in a VACUUM run, using the appropriate option.

+

REINDEX

+

REINDEX rebuilds the indexes in case these have degenerated caused +by unusual data patterns inserted. This can happen for example if you insert +many rows with increasing index values, and delete low index values.

+

The RECREATE option doesn't call the REINDEX SQL command internally, +instead it drops the existing table and recreates it according to the current index +definition.This doesn't lock the table exclusively, as REINDEX does, but will lock +write access only. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/openssl.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/openssl.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/openssl.html (revision 1448) @@ -0,0 +1,71 @@ + + + + + +The OpenSSL Licence + + + +

pgAdmin uses code from the OpenSSL project to provide support for +SSL encrypted connections. The OpenSSL licence is included below:

+ +

Copyright (c) 1998-2004 The OpenSSL Project. +All rights reserved.

+ +

+Redistribution and use in source and binary forms, with or without +modification, are permitted provided that the following conditions +are met: +

+
    +
  1. Redistributions of source code must retain the above copyright + notice, this list of conditions and the following disclaimer. +
      +
  2. Redistributions in binary form must reproduce the above copyright + notice, this list of conditions and the following disclaimer in + the documentation and/or other materials provided with the + distribution. +
      +
  3. All advertising materials mentioning features or use of this + software must display the following acknowledgment: + "This product includes software developed by the OpenSSL Project + for use in the OpenSSL Toolkit. (http://www.openssl.org/)" +
      +
  4. The names "OpenSSL Toolkit" and "OpenSSL Project" must not be used to + endorse or promote products derived from this software without + prior written permission. For written permission, please contact + openssl-core@openssl.org. +
      +
  5. Products derived from this software may not be called "OpenSSL" + nor may "OpenSSL" appear in their names without prior written + permission of the OpenSSL Project. +
      +
  6. Redistributions of any form whatsoever must retain the following + acknowledgment: + "This product includes software developed by the OpenSSL Project + for use in the OpenSSL Toolkit (http://www.openssl.org/)" +
+

+THIS SOFTWARE IS PROVIDED BY THE OpenSSL PROJECT ``AS IS'' AND ANY +EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE +IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR +PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OpenSSL PROJECT OR +ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, +SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT +NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; +LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) +HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, +STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) +ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED +OF THE POSSIBILITY OF SUCH DAMAGE. +

+
+

+This product includes cryptographic software written by Eric Young +(eay@cryptsoft.com). +This product includes software written by Tim +Hudson (tjh@cryptsoft.com). +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/restore.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/restore.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/restore.html (revision 1448) @@ -0,0 +1,51 @@ + + + + + +Restore + + + + +

Restore

+
+

+The restore dialogue presents a somewhat simplified interface to the +PostgreSQL pg_restore +tool. +

+

+After you selected a valid backup file, pgAdmin will read the +contents of the file when you press the View button. This may take +some time, dependend on the size of the file. You can watch the +progress on the Messages tab. After the examination has completed, +pgAdmin will display the contents on the Contents tab. +

+

+Intentionally, the tool will not create the database to be +restored. In order to restore a database, first create it using +pgAdmin, and then start the restore tool with that fresh database +selected. The data will be restored to that database. +

+

+You can restore a single object, when in restore database mode (this +is displayed in the title bar, as in this example). After +examining the backup file, you can select the desired table from the +Contents tab, and check the Single Object box. Only that table will be +restored. +

+

+You can select a table as restore destination. pgAdmin will +restore its data if it is present in the backup file. +

+

+In order to use backup, the pg_restore tool must be accessible by +pgAdmin. This can be accomplished by having it locatable using the +path, or by copying it into the same directory where the pgadmin3 +executable resides. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab5.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab5.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options-tab5.html (revision 1448) @@ -0,0 +1,30 @@ + + + + + +pgAdmin Options - Tab 5 (Display) + + + + +

pgAdmin Options - Tab 5 (Display)

+ +
+ +

Show System Objects in the treeview - this option allows objects +such as system schemas (e.g. pg_temp*) and system columns (e.g. xmin, +ctid) to be included or excluded in the browser tree. +

+ +

+The list of check boxes is used to select which object types to show in the +browser tree. By default, only the most commonly used object types are +shown. Reducing the number of object types shown can increase the speed +of pgAdmin when querying the system catalogs. Use the Default button +to reset the list to it's default settings. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/debugger.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/debugger.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/debugger.html (revision 1448) @@ -0,0 +1,47 @@ + + + + + +pgAdmin Debugger + + + + +

pgAdmin Debugger

+ +
+ +

The debugger may be used to debug pl/pgsql functions in PostgreSQL, +as well as EDB-SPL functions, stored procedures and packages in +EnterpriseDB. +

+ +

In order to use the debugger, a plugin is required on your server. This +is included by default with EnterpriseDB, and is expected to be released +for PostgreSQL in mid-2007. +

+ +

The debugger may be used for both in-context and direct debugging. To +debug an object in-context, right click it in the pgAdmin browser treeview, +and select the "Global breakpoint" option. The debugger will then wait for +the next session to execute the object, and break on the first line of +executable code. To directly debug an object, right click it and select +the "Debug" option. The debugger will prompt you for any parameter values +that may be required, invoke the object, and break on the first line +of executable code.

+ +

Once the debugger session has started you can step through the code using +the menu options, keyboard shortcuts or toolbar buttons. Breakpoints may be +set or cleared by clicking in the margin of the source window, or by clicking +on the desired code line and using the "Toggle breakpoint" button or menu +option. If you step into other functions, the Stack pane may be used to navigate +to different stack frames - simply select the frame you with to view.

+ +

When the debugger has reached the end of the executable code, if running in-context +it will wait for the next call to the function, otherwise it will prompt for +parameter values again and restart execution. You may exit the debugger at any +time.

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent.html (revision 1448) @@ -0,0 +1,28 @@ + + + + + +pgAgent + + + + +

pgAgent

+

Introduced in pgAdmin III v1.4, pgAgent is a job scheduling agent for +PostgreSQL, capable of running multi-step batch/shell and SQL tasks on +complex schedules.

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.css =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.css (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.css (revision 1448) @@ -0,0 +1,64 @@ +BODY +{ + BACKGROUND-COLOR: #ffffff; + BORDER-BOTTOM: medium none; + BORDER-LEFT: medium none; + BORDER-RIGHT: medium none; + BORDER-TOP: medium none; + COLOR:black; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 12px; + FONT-STYLE: normal; + FONT-VARIANT: normal; +} + +th +{ + COLOR: #ffffff; + BACKGROUND-COLOR: #6884a4; + TEXT-DECORATION: none; + FONT-WEIGHT: 600; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 13px; + TEXT-ALIGN: left; +} + +td +{ + BACKGROUND-COLOR: #ffffff; + COLOR: black; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 12px; + FONT-STYLE: normal; + FONT-VARIANT: normal; +} + +p, li, ul, ol, center, dt, dd, dl +{ + BACKGROUND-COLOR: #ffffff; + COLOR: black; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 12px; + FONT-STYLE: normal; + FONT-VARIANT: normal; +} + +#TablePar +{ + BACKGROUND-COLOR: #ffffff; + COLOR: black; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 12px; + FONT-STYLE: normal; + FONT-VARIANT: normal; +} + +#WhiteTablePar +{ + BACKGROUND-COLOR: #ffffff; + COLOR: black; + FONT-FAMILY: verdana, helvetica, sans-serif; + FONT-SIZE: 12px; + FONT-STYLE: normal; + FONT-VARIANT: normal; +} Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/commandline.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/commandline.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/commandline.html (revision 1448) @@ -0,0 +1,50 @@ + + + + + +Command Line Parameters + + + + +

Command Line Parameters

+

+There are a number of command line options that may be passed to the pgAdmin executable +when starting it. +

+ + + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/team.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/team.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/team.html (revision 1448) @@ -0,0 +1,64 @@ + + + + + +The pgAdmin Development Team + + + + +

The pgAdmin Development Team

+

Version 2.0, 25 July 2007

+
    +

  1. Purpose

    +

    The pgAdmin Development Team exists for 2 reasons:

    +
      +

    1. To manage and maintain the + pgAdmin Project +

      +

    2. To ensure that pgAdmin remains + freely available to anyone that wants it. +

      +
    +

  2. Structure

    +

    The foundation consists of the Project Leader and Members.

    +
      +

    1. Project Leader: The + Project Leader is Dave Page, founder and primary developer of the + software. The Project Leader is also considered a Core Developer. +

      +

    2. Members: Members can be + any contributor to the project who accepts an invitation from the + existing Development Team. +

      +
    +

  3. Division of Responsibilities

    +

    Any major decision regarding the Project must be voted on by the + Development Team. Any vote will be made via email through the relevant + mailling list. Responses not received within 2 weeks will be discounted + from the vote.

    In the case of a hung vote, the Project Leader shall + cast the deciding vote.

    +

  4. People

    +

    The pgAdmin Development Team includes the following people:

    + + +

    The following people no longer work on the project, but we remain grateful for their past contributions:

    + + +
+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/extend.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/extend.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/extend.html (revision 1448) @@ -0,0 +1,66 @@ + + + + + +Extended features + + + + +

Extended features

+ +

pgAdmin III's functionality can be further enhanced using the adminpack contrib +module for PostgreSQL. This is a library of additional functions that may be installed +on your server which allows pgAdmin to offer additional features, such as:

+ + + +

The adminpack is installed and activated by default if you are running the +'official' pgInstaller distribution of PostgreSQL for Windows, however, if you are running +any other version of PostgreSQL you will need to manually install it. To do so, +simply copy the /xtra/admin or /xtra/admin81 (for PostgreSQL 8.1 and above) directory +from the pgAdmin source distribution to the /contrib directory of your pre-configured PostgreSQL +source tree. If you don't have the pgAdmin source code, you can download the adminpacks +here.

+ +

Run the following commands (substituting admin for admin81 +if required):

+ +
+    # cd $PGSRC/contrib/admin
+    # make all
+    # make install
+
+ +

The module should now be built, and installed into your existing PostgreSQL installation. +to be used, you must now install the module into the database you use as pgAdmin's Maintenance +DB (normally postgres, though you may wish to use a different database). To do so, +locate the admin.sql or admin81.sql file installed in the previous step - normally +this may be found in /usr/local/pgsql/share/contrib/ and run it against your database. You will +normally need to do this as the PostgreSQL superuser:

+ +
+    $ psql postgres < /usr/local/pgsql/share/contrib/admin.sql
+
+ +

The next time you connect to the server with pgAdmin, it will detect the presence of the adminpack +and offer full functionality.

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/guruhints.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/guruhints.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/guruhints.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + +Guru Hints + + + + +

Guru Hints

+

+pgAdmin III has some functions included which should help to implement healthy +and good performing databases. They are the result of the long experience of the +developers worldwide, and the design problems commonly observed. +

+

+If pgAdmin III thinks it has a valuable hint for you, it will pop up a guru hint unless +you have chosen to suppress that individual hint or all hints (see +options). You can bring up the hint by pressing +the hint button in the toolbar at any time, if enabled. +

+
+

+This is an example of a guru hint, as it appears when trying to connect to a +non-running or misconfigured PostgreSQL server. +

+

+If you check 'do not show this hint again', the automatic popup of the individual hint will be +suppressed in the future, until it is reset in the +options. Error messages will still appear, but without +the extended information as privided by the hints. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/connect.html (revision 1448) @@ -0,0 +1,89 @@ + + + + + +Connect to Server + + + + +

Connect to Server

+ +
+ +

Use this dialog to add a new server connection to the root of the +pgAdmin tree. +

+

+If you're experiencing connection problems, check the connection problems page. +

+

+The description is a text to identify the +server in the pgAdmin tree. +

+

+The host is the IP address of the machine to contact, or the fully +qualified domain name. On Unix based systems the address field may +be left blank to use the default PostgreSQL Unix Domain Socket on +the local machine, or be set to an alternate path containing a PostgreSQL +socket. If a path is entered, it must begin with a "/". The port number +and SSL connection options may also be specified. +

+

+The maintenance DB field is used to specify the initial database that +pgAdmin connects to, and that will be expected to have the +pgAgent schema and adminpack objects +installed (both optional). On PostgreSQL 8.1 and above, the maintenance +DB is normally called 'postgres', and on earlier versions 'template1' is +often used, though it is preferrable to create a 'postgres' database for +this purpose to avoid cluttering the template database. +

+

+If you select "Store password", pgAdmin stores passwords you enter in the ~/.pgpass file under *nix or %APPDATA%\postgresql\pgpass.conf +under Win32 for later reuse. For details, see pgpass documentation. +It will be used for all libpq based tools. If you want the password removed, you can +select the server's properties and uncheck the selection any time. +

+

+The "Restore env?" option determines whether or not pgAdmin will attempt to restore the +browser environment when you reconnect to this server. If you regularly use different +databases on the same server you might want to turn this option off. +

+

The DB restriction field allows you to enter an SQL restriction that +will be used against the pg_database +table to limit the databases that you see. For example, you might enter: +datname IN ('live_db', 'test_db') so that only live_db and test_db +are shown in the pgAdmin browser. Note that you can also limit the schemas +shown in the database from the Database properties dialogue by entering a +restriction against pg_namespace. +

+The service field specifies parameters to control the database service +process. Its meaning is operating system dependent. +

+

+If pgAdmin is running on a Windows machine, it can control the +postmaster service if you have enough access rights. Enter the name of +the service. In case of a remote server, it must be prepended by the +machine name (e.g. PSE1\pgsql-8.0). pgAdmin will automatically +discover services running on your local machine. +

+If pgAdmin is running on a Unix machine, it can control processes +running on the local machine if you have enough access rights. Enter a +full path and needed options to access the pg_ctl program. When +executing service control functions, pgAdmin will append +status/start/stop keywords to this. Example:
+sudo /usr/local/pgsql/bin/pg_ctl -D /data/pgsql +

+ +

+You can unckeck the "Connect now" checkbox if you don't want the connection +to the server being established immediately, but only registered for later use. In this +case, the connection parameters won't be validated. +

+

+This dialog can be launched at a later time to correct or add +parameters by executing "properties" when the server is selected. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-install.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-install.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgagent-install.html (revision 1448) @@ -0,0 +1,120 @@ + + + + + +pgAgent Installation + + + + +

pgAgent Installation

+

pgAgent runs as a daemon on *nix systems, and a service on Windows systems. +In the majority of cases it will run on the database server itself - it is +for this reason that pgAgent is not automatically setup when pgAdmin is +installed. In some cases however, it may be preferable to run pgAgent on +multiple systems, against the same database - individual jobs may be targetted +at a particular host, or left for execution by any host. Locking prevents +execution of the same instance of a job by multiple hosts.

+ +

Database setup

+

pgAgent stores it's configuration in the "postgres" database in your cluster. This +database exists by default in PostgreSQL 8.1 versions, for earlier versions +you need to create the database yourself. The database +must have the pl/pgsql procedural language installed - PostgreSQL's +'createlang' program can do this if required.

+ +

Connect to the "postgres" database (once created if needed), and open the SQL tool. +Select the File -> Open option from the menu and find the 'pgagent.sql' +script installed with pgAdmin. The installation location for this file +varies from operating system to operating system, however it will normally +be found under 'C:\Program files\pgAdmin III' on Windows systems (or +'C:\Program files\PostgreSQL\8.x\pgAdmin III' if installed with the PostgreSQL server installer), +or '/usr/local/pgadmin3/share/pgadmin3' or '/usr/share/pgadmin3' on *nix +systems. Once the file is loaded, click the 'Run' button to execute the script.

+ +

The script will create a number of tables and other objects in a schema called +'pgagent'.

+ +

Daemon installation on *nix

+

To install the pgAgent daemon on a *nix system, you will normally need to have root +privileges to modify the system startup scripts - doing so is quite system specific +so you should consult your system documentation for further information.

+ +

The program itself takes few command line options - most of which are only +needed for debugging or specialised configurations:

+ +
+Usage:
+  /path/to/pgagent [options] <connect-string>
+  
+options:
+  -f run in the foreground (do not detach from the terminal)
+  -t <poll time interval in seconds (default 10)>
+  -r <retry period after connection abort in seconds (>=10, default 30)>
+  -s <log file (messages are logged to STDOUT if not specified)>
+  -l <logging verbosity (ERROR=0, WARNING=1, DEBUG=2, default 0)>
+
+ +

The connect string required is a standard PostgreSQL libpq connection +string (see the PostgreSQL +documentation for further details). For example, the following +command lilne will run pgAgent against a server listening on the localhost, +using a database called 'pgadmin', connecting as the user 'postgres':

+ +
+/path/to/pgagent hostaddr=127.0.0.1 dbname=pgadmin user=postgres
+
+ +

Service installation on Windows

+

pgAgent is able to self-install itself as a service on Windows systems. +The command line options available are similar to those on *nix systems, but +include an additional parameter to tell the service what to do:

+ +
+Usage:
+  pgAgent REMOVE <serviceName>
+  pgAgent INSTALL <serviceName> [options] <connect-string>
+  
+  options:
+    -u <user or DOMAIN\user>
+    -p <password>
+    -d <displayname>
+    -t <poll time interval in seconds (default 10)>
+    -r <retry period after connection abort in seconds (>=10, default 30)>
+    -l <logging verbosity (ERROR=0, WARNING=1, DEBUG=2, default 0)>
+
+ +

The service may be quite simply installed from the command line as follows +(adjusting the path as required):

+ +
+"C:\Program Files\pgAdmin III\pgAgent" INSTALL pgAgent -u postgres -p secret hostaddr=127.0.0.1 dbname=pgadmin user=postgres
+
+ +

The service may then be started from the command line using net start pgAgent, +or from the Services control panel applet. Any logging output or errors will be +reported in the Application event log.

+ +

Security concerns

+

pgAgent is a very powerful tool, but does have some security considerations +that you should be aware of:

+ +

Database password - DO NOT be tempted to include a password in +the pgAgent connection string - on *nix systems it may be visible to all users +in 'ps' output, and on Windows systems it will be stored in the registry in +plain text. Instead, use a libpq ~/.pgpass file to store the passwords for +every database that pgAgent must access. Details of this technique may be +found in the PostgreSQL documentation.

+ +

System/database access - all jobs run by pgAgent will run with the +security privileges of the pgAgent user. SQL steps will run as the user that +pgAgent connects to the database as, and batch/shell scripts will run as the +operating system user that the pgAgent service or daemon is running under. +Because of this, it is essential to maintain control over the users that are +able to create and modify jobs. By default, only the user that created the +pgAgent database objects will be able to do this - this will normally be the +PostgreSQL superuser.

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/options.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +pgAdmin Options + + + + +

pgAdmin Options

+

pgAdmin has a selection of configuration options to help it work +as you prefer. If you think of an additional feature that should be +optional or configurable though, please send the developers an email +at pgadmin-hackers@postgresql.org.

+

Normally pgAdmin will be configured from within the application. +The Options dialogue can be found under File -> Options. +

For help on each of the individual tabs, please click the +appropriate link below.

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-set.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-set.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-set.html (revision 1448) @@ -0,0 +1,69 @@ + + + + + +Creating sets and subscriptions + + + +

Creating sets and subscriptions

+ + + +

Create replication set

+
+
+

+Slony-I groups tables and sequences it has to replicate from a master to slaves into +replication sets. The set is created on the source node of the data. +

+ + +

Define replicated table

+
+
+

+If the source table has triggers defined on it, these have to be disabled on replication +target nodes. But in replication environments, the master and slave roles might exchange, +so it is necessary to enable and disable triggers in those situations. The 'Trigger' page +allows selection of triggers that Slony-I should enable and disable if necessary. +

+

+Attention: If a table you'd like to have replicated doesn't appear in the table combobox, +this usually means that the table lacks a unique index. Slony-I requires that each row +in tables that are to be replicated must be uniquely identifyable. Usually, this should be done +with a primary key, but for replication purposes a unique key is satisfactory. +

+

+While Slony-I has a helper function to define intermediate unique keys, this is not supported +with tables added to replication sets with pgAdmin III. We strongly recommend defining +a primary key on the tables to be replicated. +

+ + +

Define replicated sequence

+
+
+

+The sequence allows adding sequences to a replication set. +

+ + +

Subscribe a replication set

+
+
+

+After a replication set has been defined, it can be subscribed. Subscriptions have to +be created on the source node (note: on Slony-1 before v1.1, this had to be performed on the +target node). +

+After a set has been subscribed, its table and sequence definition can't be changed +any more. To add more tables, you can create a set that includes the additional tables +and sequences you'd like to have added to the first replication set, then subscribe +exactly the same receiver nodes to it, and finally use +Merge to merge both sets +into one. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/reports.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/reports.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/reports.html (revision 1448) @@ -0,0 +1,65 @@ + + + + + +Report Tool + + + + +

Report Tool

+ +

+pgAdmin includes a simple reporting engine which allows you to quickly +generate reports from the queries you write in the +Query Tool, or from objects or collections of objects in the main +application Window - for example, you can create a report of the properties +of any object, or a list of functions in a schema. To create a report, +select a node in the browser treeview, and select the report to create from +the context menu, or from the Reports submenu of the Tools menu. To create +a report in the Query Tool, select the Quick Report option from the File menu. +

+ +
+ +

Each report contains a title and optional notes that can be modified before +the report is produced. In addition, you may select whether or not to include +any SQL that may be relevant to the report you have select. +

+ +

Reports are generated internally in XML, however pgAdmin can apply an XML +stylesheet to the report at processing time to format the output as required. A +default stylesheet is built-in which produces HTML output. With the HTML output +option selected, you can opt to embed the default CSS stylesheet (which will +render the report in the same colors as the pgAdmin website), to embed an external +stylesheet into the report, or to link to an external stylesheet. The following +class/object ID's are used:

+ + + +
+ +

When generating reports in XML format, you can opt to output plain XML, +XML linked to an external XSL stylesheet, or to process the XML using an +external stylesheet and save the resulting output. This allows complete +flexibility to format reports in any way.

+ +

The default XSL stylesheet used to render +XHTML output can be used as a starting point for your own, and sample +XML data may also be reviewed if required. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhc =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhc (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/pgadmin3.hhc (revision 1448) @@ -0,0 +1,235 @@ + + + + + + + + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-execute.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-execute.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-execute.html (revision 1448) @@ -0,0 +1,21 @@ + + + + + +Execute DDL scripts with Slony-I + + + +

Execute DDL scripts with Slony-I

+
+
+ +

+Most schema changes that can be executed with pgAdmin III are replication-aware, i.e. +you can advise pgAdmin III to apply the change (create/alter) using the replication facilities, +simply by selecting a replication set that is subscribed to all nodes which should +receive the PostgreSQL object. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/translation_team.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/translation_team.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/translation_team.html (revision 1448) @@ -0,0 +1,32 @@ + + + Translation team + + + + +

Translation team

+

We are very grateful to those who commit time to translating pgAdmin III. Here is + the list of translators, ordered by language code: +

+

+

+ +

+ There are other translations in progress, you can check the current translation + status at our Translation + status page. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/backup.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/backup.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/backup.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Backup + + + + +

Backup

+
+

+The backup dialogue presents a somewhat simplified interface to the +PostgreSQL pg_dump tool. +You can backup a single table, a schema or a complete database, +dependent on the object you select when starting the backup +tool. +

+

+pg_dump does not support all options for all backup file +formats. Particularly, to backup blobs the PLAIN format can not be +used. Also, a PLAIN file can not be interpreted, and can not be +restored using pgAdmin. The PLAIN format will create an SQL script +that can be executed using the psql tool. For standard backup and +restore purposes, the COMPRESS and TAR options are recommended. +

+

+In order to use backup, the pg_dump tool must be accessible by +pgAdmin. This can be accomplished by having it locatable using the +path, or by copying it into the same directory where the pgadmin3 +executable resides. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/index.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/index.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/index.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +pgAdmin III + + + + +

pgAdmin III

+

pgAdmin III is a comprehensive PostgreSQL +database design and management system for *nix and Windows +systems. It is freely available under the terms of the Artistic +Licence and may be redistributed provided the terms of the +licence are adhered to. The project is managed by the pgAdmin +Development Team.

+

This software was written as a successor to the original pgAdmin +and pgAdmin II products, which though popular, had limitations in the +design that prevented them being taken to the 'next level'. pgAdmin +III is written in C++ and uses the excellent wxWidgets (formerly wxWindows) +cross platform toolkit. Connection to PostgreSQL is made using the +native libpq library.

+ + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-overview.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-overview.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/slony-overview.html (revision 1448) @@ -0,0 +1,30 @@ + + + + + +Slony-I with pgAdmin III overview + + + + +

Slony-I with pgAdmin III overview

+ +
+ +

+The Slony-I objects are integrated into pgAdmin's main object tree browser, allowing +a single interface to both database object and replication administration. +

+

+The statistics tab for the nodes collection as well as for individual nodes show +the status of the replication event queue, and allows monitoring of the functionality +of the slony cluster. +

+

+As an example, the situation shown above displays the status of a node that hasn't +been responsive for about an hour, with 381 events pending to be replicated to that +node. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/bugreport.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/bugreport.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/bugreport.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Bug Reporting + + + + +

Bug Reporting

+ +

If you think you encountered a bug in pgAdmin III, please check the +following:

+ +

Ahh, so you've found a new one then? +

+

Post your report to support +mailing list, include the following informations:

+ +Please do not send an email directly to one of the programmers; they might miss it, or even be the wrong person altogether. +Using the mailing list guarantees that your request isn't lost and will be answered in a timely fashion. +

After a bug has been reported on the mailing list as being fixed, +it might take one or two days until it has made it into the +distribution tarballs, please be patient.

+

Thanks for giving pgAdmin3 a chance!

+

The pgAdmin Development Team

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/appendices.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/appendices.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/en_US/appendices.html (revision 1448) @@ -0,0 +1,26 @@ + + + + + +Appendices + + + + +

Appendices

+ + + +

pgAdmin includes software from the OpenSSL and MIT Kerberos projects:

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,29 @@ + + + + + +Guru nasveti + + + + +

Enkodiranje podatkovne zbirke

+

+Podatkovna zbirka je ustvarjena tako, da za shranjevanje uporablja SQL_ASCII nabor. Ta nabor +je definiran le za 7-bitne znake. Za znake z nastavljenim 8. bitom (ne-ASCII znaki 127-255) pomen ni +določen. Posledično zato ni možno pretvarjanje podatkov v drugačne nabore. +

+

+Če shranjujete ne-ASCII znake v podatkovni zbirki, vam priporočamo, da uporabite ustrezen nabor +znakov, ki vsebuje vse znake, ki jih uporabljate. S tem pridobite tudi možnost pretvorbe podatkov +v drugačne načine zapisa. Če shranjujete ne-ASCII znake v SQL_ASCII podatkovno zbirko, tvegate, da boste +naleteli na nenanavadne znake pri zapisu ali branju podatkov, do katerih bo prišlo pri pretvorbi. +To vam lahko povzroči obilo glavobolov, ko boste morali dostopati do podatkovne zbirke z uporabo +drugih odjemalcev in gonilnikov. +

+

+Za večino namestitev se Unicode (UTF8) nabor izkaže kot najbolj fleksibilen in uporaben. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-ident.html (revision 1448) @@ -0,0 +1,38 @@ + + + + + +Guru nasveti + + + + +

Ident avtentikacija spodletela

+

+Strežnik ne sprejme trenutnega uporabnika: strežnik sporoča +

+

+ +

+

+Če se pojavi to sporočilo, je vnos v pg_hba.conf datoteki za kombinacijo vašega naslova, uporabnika ter baze +nastavljen na "ident" avtentikacijo. Nekatere distribucije, npr. Debian, imajo to že v privzetih +nastavitvah. Za uspešno izvršitev ident avtentikacije je potrebno nekaj dodatnih nastavitev; o tem ti lahko +preberete v PostgreSQL dokumentaciji. Za začetnike je morda bolj primerno nastaviti drugačen način preverjanja +pristnosti; MD5 kriptirana gesla so dobra izbira, ki se jo lahko določi z vnosom v datoteko pg_hba.conf, denimo: +

+

+host all all 192.168.0.0/24 md5 +

+

+Ta primer dovoli vsem uporabnikom, ki prihajajo iz zasebnega omrežja 192.168.0.0/24 in se identificirajo z MD5 +kodiranim geslom, dostop do vseh baz. +

+

+Za urejanje pg_hba.conf nastavitvene datoteke lahko uporabite namenski urejevalnik, vgrajen v pgAdmin III. +Ko spremenite to datoteko, je potrebno sprožiti osvežitev nastavitev, kar lahko opravite z ukazom pg_ctl ali z +zaustavitvijo in ponovnim zagonom strežniškega procesa. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/vacuum.html (revision 1448) @@ -0,0 +1,33 @@ + + + + + +Guru nasveti + + + + +

Priporočeno je pognati VACUUM

+

+Ocenjeno število vrstic v tabeli "" precej odstopa od dejanskega števila. Na tej tabeli +je priporočljivo pognati VACUUM ANALYZE. +

+Namesto ročnega zagona VACUUM ANALYZE ukaza na tej tabeli (uporabite lahko pgAdminov III menu za vzdrževanje) +lahko razmislite o rednem ali samodejnem zagonu VACUUM ANALYZE. To lahko dosežete z uporabo aplikacij za načrtovano +izvajanje opravil. PostgreSQL tudi vsebuje pg_autovacuum demona, ki sledi opravljenim spremembam na podatkovni zbirki +ter po potrebi izvrši VACUUM ukaze. V večini primerov je pg_autovacuum najboljša izbira. +



+Čemu je VACUUM sploh namenjen, za kaj je dober? +

+PostgreSQLov načrtovalnik (planner) stavkov se odloča glede na predpostavke, ki jih dobi iz ocen, kot je tudi +število vrstic. Če je dejansko število vrstic zelo različno od ocenjenega, se načrtovalnik lahko narobe odloči, +kar se lahko odraža v neoptimalnem načrtu izvedbe stavka. To se, posledično, lahko odrazi v počasnejšem +delovanju. +

+PostgreSQLovo shranjevanje potrebuje VACUUM za fiksne IDje transakcij na tabelah. Poleg tega se +nerabljene vrstice iz posodobitev ali odstranitev ne počistijo, dokler se na tabeli ne izvede VACUUM ukaz. +Podrobnejše informacije lahko najdete v dokumentaciji, le kliknite na gumb za pomoč. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/instrumentation.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru nasveti + + + + +

Dodatne / podporne funkcije na strežniku

+

+Na tem strežniku ni na voljo dodatnih / podpornih funkcij. +

+

+pgAdmin III uporablja nekatere podporne funkcije, ki po privzetih nastavitvah niso na voljo +v vseh PostgreSQL različicah. Le-te omogočajo nekaj funkcionalnosti, ki olajšajo življenje +pri ravnanju z dnevniškimi ter nastavitvenimi datotekami. +

+

+Ko nameščate PostgreSQL 8.0 ali novejšega z uporabo Windows namestitvenega vmesnika, +pri izbiri komponent označite tudi "admin" možnost. +

+

+Pri prevajanju iz izvorne kode lahko ustrezne datoteke najdete v xtra poddirektoriju +pgAdmin izvornega drevesa. Za PostgreSQL 8.0, prekopirajte admin direktorij iz postgresql +contrib izvornega direktorija, potem sledita se make in make install. Za PostgreSQL 8.1 +uporabite admin81 direktorij. Ko je modul nameščen, je potrebno z uporabo admin.sql +(admin81.sql za PostgreSQL 8.1) skripta ustvariti ustrezne funkcije v glavni / vzdrževalni +podatkovni zbirki. Datoteki admin.sql oz. admin81.sql se običajno nahajata v pgsql share +direktoriju (npr. /usr/local/pgsql/share). +

+

+Dodatne oziroma podporne funkcije srtežnika niso podprte za PostgreSQL 7.3 in 7.4. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,23 @@ + + + + + +Guru nasveti + + + + +

Urejanje tabele brez primarnega ključa

+

+Ker tabela nima primarnega ključa ali OID-jev, je možen le pregled podatkov. +Brez primarnega ključa vstavljanje novih vrstic ali urejanje obstoječih v orodju za urejanje podatkov ni možno. +

+

+Da bi lahko urejal podatke pgAdmin III potrebuje primarni ključ na tabeli, kar je tako ali tako dobra praksa pri delu +s podatkovnimi bazami. Kot alternativa je pri kreiranju tabele na voljo možnost OID (WITH OIDS). Opozoriti velja, da OID-ji +ne zagotavljajo unikatnosti po dolgotrajnejši rabi, zato je njih uporaba namesto primarnih ključev ponavadi +rezervna izbira. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-hba.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Guru nasveti + + + + +

Dostop do baze zavrnjen

+

+Strežnik ne dovoli dostopa do baze: strežnik sporoča +

+

+ +

+

+Da bi lahko dostopali do podatkovne baze na PostgreSQL strežniku, je potrebno najprej dodeliti vašemu odjemalcu +dostop do strežnika (Host Based Authentication). PostgreSQL bo pregledal datoteko pg_hba.conf, če se v njej +nahaja vzorec, ki se ujema vašemu omrežnemu naslovu / uporabniškemu imenu / bazi in če je le-ta omogočen, preden +se preverijo SQL GRANT seznami dostopov. +

+

+Začetne nastavitve v datoteki pg_hba.conf so zelo omejujoče, da bi se izognili varnostnim luknjam, ki jih lahko +povzročijo nepregledane, vendar obvezne sistemske nastavitve. Najbrž boste morali dodati vrstico, podobno tej +

+

+host all all 192.168.0.0/24 md5 +

+

+Ta primer dovoli vsem uporabnikom, ki prihajajo iz zasebnega omrežja 192.168.0.0/24 in se identificirajo z MD5 +kodiranim geslom, dostop do vseh baz. +

+

+Za urejanje pg_hba.conf nastavitvene datoteke lahko uporabite namenski urejevalnik, vgrajen v pgAdmin III. +Ko spremenite to datoteko, je potrebno sprožiti osvežitev nastavitev, kar lahko opravite z ukazom pg_ctl ali z +zaustavitvijo in ponovnim zagonom strežniškega procesa. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/autovacuum.html (revision 1448) @@ -0,0 +1,30 @@ + + + + + +Guru nasveti + + + + +

Priporočljiva je uporaba pg_autovacuum

+

+Proces pg_autovacuum, poprej dodatna storitev, je od PostgreSQL-a 8.1 dalje +vključen v osnovni paket. Samodejno bo zagnal VACUUM, ko pride do sprememb +določene količine podatkov. +

+

+Redna uporaba VACUUM-a je na PostgreSQL strežnikih pogoj za konsistentnost podatkov ter +ohranitev velike zmogljivosti strežnika. Za začetek je priporočljivo omogočiti pg_autovacuum +prikriti proces, in sicer z nastavitvijo možnosti 'autovacuum', 'stats_start_collector' in 'stats_row_level', +nahajajo se v datoteki postgresql.conf, na vrednost 'on'. Ob zanemarljivih vplivih na delovanje zaradi +sledenja sprememb podatkov pridobite samodejno izvajanje VACUUM-a. +

+

+Za prilagoditev delovanja procesa pg_autovacuum je potrebno nastaviti njegove parametre v datoteki +postgresql.conf. Nastavitve so lahko ali globalne ali prirejene posameznim tabelam; več informacij je na voljo +v dokumentaciji. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/conn-listen.html (revision 1448) @@ -0,0 +1,46 @@ + + + + + +Guru nasveti + + + + +

Strežnik ne posluša

+

+Strežnik ne sprejema povezav: povezovalna knjižnica sporoča +

+

+ +

+

+Če naletite na to sporočilo, preverite ali je na strežniku, na katerega se poskušate povezavi, +PostgreSQL zagnan in posluša na navedenih vratih. Preverite, če je vse v redu s povezljivostjo +med vašim odjemalcem in strežnikom z orodji, kot so ping ipd. Ali je vaše omrežje / VPN / SSH tunel / +požarni zid pravilno nastavljen? +

+

+Iz varnostnih razlogov PostgreSQL ne posluša na vseh IP naslovih, ki jih ima na voljo na sistemu, +kjer teče. Da bi lahko do strežnika dostopali preko omrežja, je potrebno najprej omogočiti poslušanje +na določenih naslovih. +

+

+Pri PostgreSQL strežnikih od različice 8.0 dalje se ta nadzor opravlja z uporabo "listen_addresses" parametra +v datoteki postgresql.conf. Tu lahko navedete seznam IP naslovov, na katerih naj strežnik posluša ali preprosto +uporabite '*' za poslušanje na vseh IP naslovih, ki so na voljo. Za starejše različice strežnikov (7.3 ali 7.4) se v ta namen +nastavi parameter "tcpip_socket" na vrednost 'true'. +

+

+Za urejanje datoteke postgresql.conf lahko uporabite v pgAdmin III vgrajen namenski urejevalnik te datoteke. Po +opravljenih spremembah v tej datoteki je potrebno strežnik ponovno zagnati, da se spremembe uveljavijo. +

+

+Če ste temeljito preverili nastavitve, to sporočilo pa se še vedno pojavlja, je vseeno zelo malo verjetno, da +ste naleteli na nenavadno obnašanje ali težavo PostgreSQLa. Najverjetneje gre za težave na nivoju omrežja, +morda nastavitve požarnega zidu ipd. Prosimo, če temeljito preverite nastavitve, preden PostgreSQL +skupnosti posredujete sporočilo o napaki. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/fki.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +Guru nasveti + + + +

Indeksi na tujih ključih

+

+Tuji ključ se uporablja za logično povezavo ter omejevanje sprememb, ki se lahko izvajajo na dveh tabelah. +

+

+Začne se že pri glavni tabeli, na katero se kasneje sklicujemo. Ta potrebuje primarni ključ (pravzaprav +referencirani stolpci samo ne smejo biti brez vrednosti, pokrivati pa jih mora preverjanje unikatnosti, vseeno pa +je priporočljivo imeti primarni ključ). Druga tabela je odvisna od referenčne tako, da se morajo vrednosti v stolpcu, +ki ga pokriva tuji ključ, ujemati z vrednostmi v stolpcu glavne tabele. Omejitev velja pri vnosu, izbrisu ali urejanju +zapisov. Odvisna tabela je referencirana tabela tujega ključa. +

+

+Tuji ključ lahko omejuje tudi referenčno tabelo, ne le referencirane. Vrste omejitev so lahko RESTRICT, CASCADE ali SET NULL. +To pomeni, da če se v glavni/referenčni tabeli vrstica spremeni (uredi ali odstrani), se pri vseh referenciranih tabelah preveri, +če se operacijo lahko izvede in če je ob tem morda potrebno izvesti še kakšen dodaten ukaz. Za več informacij o tujih +ključih si oglejte PostgreSQL dokumentacijo. +

+

+To pomeni, da se ob spremembi določene vrstice v referenčni tabeli izvede branje v referenciranih tabelah, z +uporabo stolpcev s tujimi ključi kot ključi dostopa. Posledično je dobro pazljivo zasnovati zgradbo tabel, da bi se +zagotovilo dobro delovanje. Za hitrejše branje podatkov je v večini primerov priporočljiva postavitev indeksov. +PostgreSQL v to nikakor ne sili uporabnikov, zato je postavitev indeksa odvisna od snovalca podatkovne zbirke. +

+

+Zavoljo priročnosti pgAdmin III ponuja možnost, ki ob ustvarjenju zunanjega ključa samodejno preveri za uporabnimi indeksi +in po potrebi ustvari novega. Kot pri vseh indeksih, so tudi tu redki primeri, kjer lahko to vpliva na malenkost +počasnejše delovanje, vendat v splošnem drži, da je imeti en indeks premalo mnogo bolj upočasni delovanje, kot en preveč. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,26 @@ + + + + + +Guru nasveti + + + + +

Unicode enkodiranje na Win32 strežniku

+

+Podatkovna zbirka je ustvarjena za uporabo Unicode (UTF8) nabora za shranjevanje podatkov +in jo uporablja PostgreSQL strežnik 8.0 na Win32 sistemu. +

+

+PostgreSQL 8.0, Win32 implementacija, ne more razvrščati znakovnih nizov po ustreznem zaporedju, +ker operacijski sistem ne ponuja dovoljšnje podpore v ta namen. +

+

+Za to namestitev je priporočljivo uporabiti bolj specifičen nabor znakov, ki je najbolj primeren +za vnešene podatke, zagon gruče na drugem operacijskem sistemu ali nadgraditev podatkovne gruče na +PostgreSQL 8.1, ki vsebuje dodatno kodo ravno z namenom reševanja tovrstnih težav. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/pk.html (revision 1448) @@ -0,0 +1,39 @@ + + + + + +Guru nasveti + + + + +

Primarni ključi

+

+Ko gradite tabelo, imejte v mislih, kako jo boste kasneje uporabljali. V večini primerov +boste potrebovali nek identifikator, s katerim lahko enolično določite posamezne zapise. Ta +identifikator naj bo ustvarjen kot primarni ključ. Primarni ključ ne obsega nujno le enega stolpca; +lahko jih je toliko, kolikor je potrebno, da se lahko enolično določa zapise v tabeli. Če je +potrebno več stolpcev (nenapisano pravilo: več kot 3), bi bilo morda pametneje ustvariti dodatni +stolpec z ustreznim podatkovnim tipom, npr. serial ali bigserial, ki bo služil kor primarni ključ. +

+

+Le v redkih primerih se ne izplača uporaba primarnega ključa. To pomeni, da manjkajoč primarni ključ +pomeni veliko verjetnost, da tabela ni ustrezno zasnovana. Zato se tudi pojavi Guru nasvet, če kreirate +tabelo brez primarnega ključa. +

+

+Če pogledate PostgreSQL-ove sistemske tabele, boste videli, da nobena nima primarnega ključa. Čemu torej vse to? +Pravzaprav ima vsaka tabela en ali dva stolpca (navadno le OID), ki enolično določita posamezno vrstico, +s tem zadovoljita drugo pravilo za primarne ključe, ne dovolita ničel, pokrita pa sta z indeksom za hitrejši dostop. +Uporaba OID-jev ima zgodovinske razloge in navadno ni prva izbira pri oblikovanju tabel. PostgreSQL jih +uporablja zaradi združljivosti za nazaj in čeprav bi novejši pristop izrecno uporabljal primarne ključe, +se stanje najbrž ne bo več kaj dosti spreminjalo. +

+

+Kot je razvidno iz primera sistemskih tabel, se lahko unikatnost in hiter dostop doseže tudi z drugačnim pristopom, +ne le s primarnim ključem. Vseeno pa je zavoljo jasnosti zasnove podatkovnih modelov priporočljiva uporaba +primarnih ključev v ta namen. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Guru nasveti + + +

+pgAdmin III je naletel na več zadev, ki se tičejo trenutnega objekta. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/sl_SI/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# Za dodajanje namiga ga le dopiÅ¡i v novo vrstico. +# Prazne vrstice se prezrejo, vrstice, ki se začnejo s # so komentarji. +# Poba, nucej UTF-8 :) + +Z redno uporabo VACUUM-a se lahko izboljÅ¡a delovanje PostgreSQLa. +Uradni rojstni dan PostgreSQL je 8. julij. Projekt PostgreSQL je nastal leta 1996. +Prvi prototip za izvirni pgAdmin projekt se je imenoval pgManager, spisan pa je bil za PostgreSQL 6.3.2. +Podporo za pgAdmin lahko izrazite na pgadmin-support@postgresql.org dopisnem seznamu. +Odgovor na vpraÅ¡anje o Åœivljenju, Vesolju in Sploh Vsem je 42. +Člani razvojne ekipe pgAdmina prihajajo med drugim iz Velike Britanije, Francije ter ZDA. +pgAdmin II je bil preneÅ¡en preko 10,000-krat *preden* je bila na voljo različica za izdajo! +Prva stabilna različica pgAdmina II je bila preneÅ¡ena preko 30,000-krat v prvih 6 mesecih po izdaji. +Prva uradna stabilna različica pgAdmina II je bila izdana 16. januarja 2002. +Razvoj projekta pgAdmin III se je začel 29. septembra 2002. +pgAdmin je izdan pod Open Source licenco 'Artistic Licence'. +PostgreSQL v /contrib direktoriju drevesa izvorne kode vključuje Å¡tevilna uporabna orodja, datoteke in projekte. +Na dopisnem seznamu pgadmin-hackers@postgresql.org potekajo diskusije o novih funkcijah ter poteku razvoja. +Večina knjiÅŸnice pgSchema, ki jo uporablja pgAdmin II, je bila razvita na prenosniku z Windows 2000, pred TV ekranom v bliÅŸini Oxforda, v Angliji. +Svoje geslo lahko spremenite preko menija 'Datoteka', 'Spremeni geslo'. +PostgreSQL 7.2 podpira tabele brez OID stolpcev, z namenom manjÅ¡e porabe OID-jev. +V PostgreSQLu 7.2 lahko nadzirate aktivnost sistema glede na posamezno povezavo z uporabo 'SELECT * FROM pg_stat_activity'. +PostgreSQLov repertoar proceduralnih jezikov vključuje tudi pl/pgSQL, pl/TCL, pl/Perl ter pl/sh. +PostgreSQL 7.3 podpira sheme. To so posamezni imenski prostori znotraj podatkovnih zbirk. +Pano z definicijami vsebuje z obratnim inÅŸeniringom pridobljen SQL za izbrani objekt. +pgAdmin III je popolnoma nova različica pgAdmina, napisana v C++ z uporabo wxWidgets okolja, ki omogoča izvajanje na Windows in *nix sistemih. +Domene se lahko uporabi za kreiranje predefiniranih podatkovnih tipov, ki temeljijo na bolj sploÅ¡nih osnovnih tipih. +pgAdmin III 1.0.0. je bil prvič izdan 26. septembra 2003. +Procesa postmaster ni dobro končati s 'kill -9'! +'EXPLAIN ANALYZE' ter gumb 'RazloÅŸi stavek' sta dobra prijatelja, ko je potrebno optimirati SQL stavke. +PostgreSQLov načrtovalec (planner) bo prezrl zahtevo po pregledu indeksov, v kolikor se tipa stolpcev, po katerih poteka zdruÅŸitev, ne ujemata. +pgAdmin III podpira SSL kriptirane povezave. +Novi prenos PostgreSQLa na Win32 sistem je prvič prestal vse regresivne preizkuse 24. decembra 2004. +Windows različica PostgreSQLa je bila v prvih petih dneh po prvi izdaji preneÅ¡ena več kot 45,000-krat! +Napaka "Don't enable the OK button when setting the ACL for as-yet-uncreated objects" je bila popravljena na 12,000 metrih viÅ¡ine nad Finsko, ko so se Andreas, Magnus in Dave vračali z Japonske po predstavitvi Slony-I in pgAdmina! +PostgreSQL 8.0 je prinesel veliko novosti, med drugim tudi točke shranjevanja, podatkovne prostore ter dolgo pričakovano različico za Windows sistem. +EnterpriseDB so pgAdmin projektu podarili Applov Powerbook, da bi pripomogli izboljÅ¡ati različico pgAdmina za Mac OS X in za njihov poenostavljeni derivatni izdelek, EDB Studio. +PostgreSQL je bil uspeÅ¡no pognan na različnih sistemih, kot so Microsoftov X Box, Sony Playstation II in Sharpovi Zaurus PDA-ji! +Japonska skupina uporabnikov PostgreSQLa (JPUG, Japan PostgreSQL Users Group) ima preko 5000 članov in Å¡e vedno raste. +pgAdmin 1.4 vsebuje grafično EXPLAIN orodje, ki omogoča pomaga laÅŸje branje in razumevanje načrtov izvedbe stavkov. +Sedeti 12 ur v letalu je zastraÅ¡ujoče dolgočasno, zato tudi piÅ¡em nove namige! +pgAgent lahko sluÅŸi za izvajanje paketnih ter SQL opravil po določenem urniku. Primera opravil sta denimo ustvarjanje časovno odvisnih delnih indeksov ali izbris starih zapisov. +Nastavitev PostgreSQLa s preveč deljenega medpomnilnika lahko slabo vpliva na delovanje, ker zniÅŸa količino pomnilnika na voljo jedru operacijskega sistema, ki ga le-ta potrebuje kot predpomnilnik datotečnega sistema. +pgAdmin 1.4 je podprt na več operacijskih sistemih kot prejÅ¡nje različice, med drugim na Å¡tevilnih Linux distribucijah, Microsoft Windows (tm), FreeBSDju, Solarisu in na sistemu Mac OS X. +Dobra praksa narekuje izgradnjo aplikacijske logike na nivoju podatkovne zbirke z uporabo funkcij ter pogledov. To pripomore k temu, da imajo različni vmesniki vedno enak vpogled na podatke in jih posodabljajo na enake načine. Kar je Å¡e bolje, za vse vmesnike je to potrebno narediti le enkrat! +Za ohranitev varnosti podatkovnih zbirk je dobro v pg_hba.conf datoteki čimbolj omejiti dostope od zunaj in vedno uporabiti kriptirane povezave, razen če nimate dobrih razlogov proti temu. +Dostop do posameznih stolpcev v tabeli se posameznim skupinam ali uporabnikom lahko omeji z odvzemom dostopa do njih in s kreiranjem novega pogleda, ki vsebuje le stolpce, do katerih imajo dostop. Če morajo uporabniki podatke tudi spreminjati, se to lahko doseÅŸe z uporabo pravil, ki priredijo spremembe pogledov na ustrezne tabele. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/Docs.vcproj =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/Docs.vcproj (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/Docs.vcproj (revision 1448) @@ -0,0 +1,1042 @@ + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

žê®Æ®wœsœX

+

žê ®Æ ®w šÏ ¥Î SQL_ASCII œs œX Àx Šs žê ®Æ¡A ³o ­Ó œs œX ³Q ©w žq ¬° ¶È Š³ 7 ­Ó Šì ªº Šr €ž¡A +·N šý µÛ šÏ ¥Î ²Ä 8 ­Ó Šì ªº Šr €ž ¡]«D ASCII Šr €ž 127-255¡^ µL ªk ©w žq¡C +Š] Š¹¡A §â Šø ªA Ÿ¹ žê ®Æ Âà Ž« ¬° šä ¥L œs œX ¬O €£ ¥i ¯à ªº¡C

+

Šp ªG ·Q Šb žê ®Æ ®w €€ Àx Šs «D ASCII žê ®Æ¡A ¿ï ¥Î €@ ­Ó ±j €j ªº žê ®Æ ®w œs œX šÓ ªí ¥Ü ¥» Ša €Æ Šr ²Å ¶°¡A +¥Š À³ žÓ ¯à °÷ €ä «ù ŠÛ °Ê Âà Ž« ¬Æ ŠÜ ·í »Ý ­n ªº ®É ­Ô ¥i ¥H šÏ ¥Î €£ ŠP «È €á ºÝ œs œX¡C +Šb SQL_ASCII žê ®Æ ®w €€ Àx Šs «D ASCII žê ®Æ¡A ¥i ¯à ·| Š] ¬° œs œX Âà Ž« °Ý ÃD ŠÓ ¹J šì ±q žê ®Æ ®w €€ Ū Œg žê ®Æ ®É ¥X ²{ ©_ ©Ç Šr ²Å ªº °Ý ÃD¡C +·í šÏ ¥Î €£ ŠP «È €á ºÝ ©M ÅX °Ê µ{ §Ç ³X °Ý žê ®Æ ®w ®É¡A ³o ±N ¥O €H «D ±` ÀY ¯k¡C

+

+¹ï €j Šh ŒÆ Šw žË ŠÓ š¥¡A Unicode ¡]UTF8¡^ œs œX Ž£ šÑ €F ³Ì ÆF ¬¡ ªº ¬Û ®e ¯à €O¡C

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-ident.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Guru Hints + + + + +

Ident ÅçÃÒ¥¢±Ñ

+

+Šø ªA Ÿ¹ µL ªk ±µ šü ·í «e ªº šÏ ¥Î ªÌ¡G Šø ªA Ÿ¹ ³ø §i +

+

+ +

+

+ +Šp ªG ¥X ²{ ³o ­Ó ®ø ®§¡A »¡ ©ú §A ªº «È €á ºÝ / šÏ ¥Î ªÌ / žê ®Æ ®w ²Õ ŠX Šb pg_hba.conf €€ ³Q ³] žm ¬° "ident" Åç ÃÒ¡C +Šb €@ šÇ µo §G ·í €€¡A €ñ Šp Debian¡A ³o ¬O ¹w ³] ³] žm¡C ¬° €F ¯à °÷ Šš ¥\ °õ Šæ °ò ©ó ident ªº Åç ÃÒ¡A »Ý ­n ¶i Šæ ÃB ¥~ ªº ³] žm ¡A œÐ ¬d ¬Ý PostgreSQL »¡ ©ú¡C +¹ï ªì ŸÇ ªÌ šÓ »¡¡A šÏ ¥Î šä ¥Š ªº Åç ÃÒ €è Š¡ ¥i ¯à §ó ŠX ŸA¡A ¥Î MD5 ¥[ ±K ±K œX ¬O ­Ó Šn ¥D ·N¡A ¥i ¥H Šb pg_hba.conf ³o ŒË °t žm¡G +

+

+host all all 192.168.0.0/24 md5 +

+

+³o ­Ó šÒ €l €¹ ³\ šp Š³ ºô žô 192.168.0.0/24 šÏ ¥Î MD5 ¥[ ±K ªº ±K œX ³s ±µ šì ©Ò Š³ šÏ ¥Î ªÌ ©M ©Ò Š³ žê ®Æ ®w¡C +

+

+§Q ¥Î Ÿã ŠX ¶i pgAdmin III ªº pg_hba.conf œs ¿è Ÿ¹ ¥i ¥H ­× §ï pg_hba.conf °t žm €å ¥ó¡A +­× §ï §¹ ²Š ¥H «á ¡A »Ý ­n šÏ ¥Î pg_ctl ³q ªŸ žê ®Æ ®w ­« ·s Ū €J °t žm ©Î ªÌ ­« ·s ±Ò °Ê žê ®Æ ®w¡C +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/vacuum.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Guru Hints + + + +

±ÀÂ˹BŠæ VACUUM

+

+"" €€ ªº ¹w Žú Šæ ŒÆ €w žg ÄY ­« °Ÿ Â÷ ¹ê »Ú Šæ ŒÆ¡A À³ žÓ Šb ³o ­Ó žê ®Æ ªí €W ¹B Šæ VACUUM ANALYZE¡C +

+°£ €F €â °Ê ¹B Šæ VACUUM ANALYZE ©R ¥O ¡] €] ¥i ¥H §Q ¥Î pgAdmin III ªº ¡uºû Å@¡v ¿ï ³æ šÓ °µ ¡^ €§ ¥~¡A +ÁÙ À³ žÓ ŠÒ Œ{ ©w ŽÁ Š³ ³W «ß ©Î ªÌ ŠÛ °Ê Ša ¹B Šæ VACUUM ANALYZE¡CšÏ ¥Î ±Æ µ{ µ{ §Ç ¥i ¥H °µ šì ³o €@ ÂI¡A +¥t ¥~ PostgreSQL €] Ž£ šÑ €F €@ ­Ó ¥s °µ pg_autovacuum ªº «á ºÝ µ{ §Ç¡A +¯à °÷ žò ÂÜ žê ®Æ ®w ªº ÅÜ €Æ šÃ Šb ŸA ·í ®É šè ŠÛ °Ê œÕ ¥Î vacuum ©R ¥O¡C +Šb €j Šh ŒÆ ±¡ ªp €U¡A pg_autovacuum ¬O ³Ì Šn ªº ¿ï ŸÜ¡C +



+VACUUM Š³€°»òŠn³B¡H + +

+PostgreSQL ªº ¬d žß ­p ¹º ®Ú ŸÚ ¹w Žú Šæ ŒÆ °µ ¥X šM ©w¡A Šp ªG ¹ê »Ú Šæ ŒÆ »P ¹w Žú Šæ ŒÆ Š³ €Ó €j ®t ²§¡A +¥i ¯à ·| §@ ¥X ¿ù »~ §P Â_¡A ³y Šš ¬d žß ­p ¹º €£ ¬O ³Ì Àu €Æ ªº ¡A ŸÉ ­P °õ Šæ ®Ä ²v ¹L §C ¡C +

+PostgreSQL žê ®Æ ®w »Ý ­n VACUUM ­× Ž_ ªí €€ ªº šÆ °È ¥æ ©ö ID¡C +¥t ¥~¡A ¥Ñ ©ó §ó ·s ©M §R °£ ŸÞ §@ ŠÓ ²£ ¥Í ªº ¹L ®É žê ®Æ ªœ šì Šb ³o ­Ó ªí €W ¹B Šæ VACUUM ©R ¥O €~ ·| ³Q ²M ²z¡C +«ö €U À° §U «ö ¶s¡A ¥i ¥H ±q œu €W €å ÀÉ €€ ¬Ý šì §ó žÔ ²Ó žê °T¡C +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/instrumentation.html (revision 1448) @@ -0,0 +1,32 @@ + + + +Guru Hints + +

ŠøªAŸ¹«ü¥O

+

+Šø ªA Ÿ¹ ¯Ê ¥F «ü ¥O šç ŒÆ¡C +

+

+pgAdmin III šÏ ¥Î ªº €@ šÇ €ä «ù šç ŒÆ €£ ¬O Šb ©Ò Š³ PostgreSQL ª© ¥» €W ¹w ³] Š³ ®Ä¡A +³o šÇ šç ŒÆ šÏ €@ šÇ œÑ Šp ³B ²z €é »x €å ¥ó ©M °t žm €å ¥ó ªº €u §@ ÅÜ ±o §ó ¥[ ² ³æ¡C +

+

+ +·í šÏ ¥Î Windows Šw žË µ{ §Ç Šw žË PostgreSQL 8.0 ©Î ªÌ §ó °ª ª© ¥» ®É¡A ¶È ¶È »Ý ­n ¿ï €€ ¡uadmin¡v ©Î ªÌ ¡udminpack¡v ŒÒ ²Õ¡C +

+

+·í ±q ·œ ¥N œX €€ œs Ķ ®É¡A ¥² ­n ªº €å ¥ó ¥i ¥H Šb ·œ ¥N œX Ÿð ªº xtra €l ¥Ø ¿ý €€ §ä šì¡C +¹ï ©ó PostgreSQL 8.0¡A ±N admin ¥Ø ¿ý «þ š© šì postgresql ·œ ¥N œX ªº contrib ¥Ø ¿ý €€¡A ±q ³o žÌ œs Ķ ©M Šw žË ¥Š¡C +¹ï ©ó PostgreSQL 8.1¡A šÏ ¥Î admin81 ¥Ø ¿ý¡C +

+PostgreSQL 8.2 ¥H €Î §ó °ª ª© ¥» Šb ¡uadminpack¡v ŒÒ ²Õ €€ ¥] §t «ü ¥O šç ŒÆ¡C +

+

+Šb ŒÒ ²Õ Šw žË €§ «á¡A ¥² ¶· šÏ ¥Î admin.sql œZ ¥» ¡]¹ï ©ó PostgreSQL 8.1 ¬O admin81.sql¡^ Šb ©Ò ­n ºû Å@ ªº žê ®Æ ®w €€ ³Ð «Ø «ü ¥O šç ŒÆ¡A +³o šÇ œZ ¥» €å ¥ó ³q ±` ¥i ¥H Šb pgsql ªº Š@ šÉ ¥Ø ¿ý ¡]šÒ Šp /usr/local/pgsql/share¡^ €€ §ä šì¡C +

+

+ÂX ®i Šø ªA Ÿ¹ «ü ¥O Šb PostgreSQL 7.3 ©M 7.4 €€ šS Š³ ³Q €ä «ù¡C +

+ Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

œs¿èšSŠ³¥DÁä(PK)ªºªížê®Æ

+

+ªí šS Š³ ¥D Áä ©Î ªÌ OID Äæ Šì ¡A ¥u ¯à ¬d ¬Ý žê ®Æ¡C +Šb šS Š³ ¥D Áä ªº ±¡ ªp €U €£ ¯à šÏ ¥Î žê ®Æ œs ¿è €u šã Ž¡ €J ·s žê ®Æ Šæ ©M ­× §ï €w žg Šs Šb ªº žê ®Æ¡C +

+

+¬° €F œs ¿è žê ®Æ¡ApgAdmin III ­n šD žê ®Æ ªí šã Š³ ¥D Áä¡A³o €] ¬O €@ ­Ó Šn ªº žê ®Æ ®w ³] ­p ²ß ºD¡C +¥t ¥~ ÁÙ Š³ €@ ºØ ŽÀ ¥N €è Š¡¡G šÏ ¥Î OID Äæ Šì ³Ð «Ø žê ®Æ ªí¡C œÐ ª` ·N OID Šb žg ¹L «Ü ªø €@ ¬q ®É ¶¡ €§ «á €£ ¯à «O ÃÒ ÁÙ ¬O °ß €@ ªº¡C +Š] Š¹ šÏ ¥Î OID §@ ¬° ¥D Áä ¶È ¶È ¬O ²Ä €G ¿ï ŸÜ¡C +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-hba.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Guru Hints + + + + +

Šsšúžê®Æ®w³Q©ÚµŽ

+

+Šø ªA Ÿ¹ €£ €¹ ³\ ³X °Ý žê ®Æ ®w¡G Šø ªA Ÿ¹ ³ø §i +

+

+ +

+

+ +³X °Ý PostgreSQL žê ®Æ ®w¡A ­º ¥ý ¥² ¶· €¹ ³\ «È €á ºÝ ¯à °÷ ³s ±µ ¥D Ÿ÷ ¡]°ò ©ó ¥D Ÿ÷ ªº »{ ÃÒ¡^¡A +µM «á Šb ©Ò Š³ SQL ³X °Ý Åv ­­ ³Q Åç ÃÒ €§ «e¡A PostgreSQL ±N ÀË ¬d pg_hba.conf €å ¥ó ¬d ¬Ý ¬O §_ Š³ »P «È €á ºÝ ªº Ša§} / ¥Î€áŠW / žê®Æ®w ¬Û ²Å ŠX ªº €è ®× Šs Šb šÃ ¥B ¬O €¹ ³\ ³X °Ý ªº¡C +

+

+¬°€FÁקK¥Ñšt²Î€Þ°_ªº€£¥²­nªºŠw¥þº|¬}¡Apg_hba.conf€€ªºªì©l³]žm€Q€ÀÄY®æ¡A¥i¥H¹³€U­±³oŒËŒW¥[³]žm¡G +

+

+host all all 192.168.0.0/24 md5 +host all all 192.168.0.0/24 md5 +

+

+³o ­Ó šÒ €l €¹ ³\ šp Š³ ºô µž 192.168.0.0/24 šÏ ¥Î MD5 ¥[ ±K ªº ±K œX ³s ±µ šì ©Ò Š³ ¥Î €á ©M ©Ò Š³ žê ®Æ ®w¡C +

+

+§Q ¥Î Ÿã ŠX ¶i pgAdmin III ªº pg_hba.conf œs ¿è Ÿ¹ ¥i ¥H ­× §ï pg_hba.conf °t žm €å ¥ó¡A +­× §ï §¹ ²Š ¥H «á¡A »Ý ­n šÏ ¥Î pg_ctl ³q ªŸ žê ®Æ ®w ­« ·s Ū €J °t žm ©Î ªÌ ­« ·s ±Ò °Ê žê ®Æ ®w¡C + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/object-editing.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/object-editing.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/object-editing.html (revision 1448) @@ -0,0 +1,32 @@ + + + + + +Guru Hints + + + + +

œs¿èµøÆ[ªí¡B¹wÀxµ{§Ç©ÎªÌšçŒÆ

+

+·í œs ¿è µø Æ[ ªí¡B ¹w Àx µ{ §Ç ©Î ªÌ šç ŒÆ ªº ¥N œX ®É¡A €£ šÏ ¥Î Šb ©ó ª« ¥ó ÄÝ ©Ê ¹ï žÜ ®Ø €W ªº €p €å ¥» ®Ø¡A ŠÓ ¬O šÏ ¥Î pgAdmin ªº œZ ¥» ¿ï ¶µ Šb ¬d žß €u šã €€ œs ¿è ¥Š¡C ¬d žß €u šã ªº œs ¿è Ÿ¹ šã Š³ ŠÛ °Ê §¹ Šš¡B ¬d §ä ŽÀ ¥N ¥\ ¯à ¥H €Î §ó €j ªº €u §@ ªÅ ¶¡¡A ³o ŒË ¥i ¯à ·| §ó ¥[ €è «K¡C

+ +

+¥i ¥H ³q ¹L Šb pgAdmin ªº ŸÉ Äý µ¡ €f §Æ ±æ œs ¿è ªº ª« ¥ó €W ÂI À» ¥k Áä¡A +µM «á ¿ï ŸÜ ¡u³Ð «Ø ž} ¥»¡v µæ ³æ¡A šÓ šÏ ¥Î œZ ¥» ¿ï ¶µ¡C Š³ ®É ¥i ¯à ¥X ²{ ¡uœZ ¥»¡v €l ¿ï ³æ¡A +šº »ò ³o ®É ­Ô ¥i ¥H ¿ï €€ ª« ¥ó¡A µM «á Šb ¡u€u šã¡v ¿ï ³æ ªº ¡uœZ ¥»¡v €l ¿ï ³æ €€ ¿ï ŸÜ ¡u³Ð «Ø œZ ¥»¡v¡C

+ +

+œs ¿è ª« ¥ó »Ý ­n ÅÜ §ó ªº ©w žq¡A µM «á šÏ ¥Î ¡u°õ Šæ ¬d žß¡v «ö ¶s Ž£ ¥æ¡C +€£ ­n §Ñ °O¡A ­× §ï µø Æ[ ªí ©Î šç ŒÆ ªº ŠW Šr ¡A ©Î ªÌ ­× §ï šç ŒÆ ©Î ¹w Àx µ{ §Ç ªº ñ ŠW ¡A +·| Šb ­ì ¥ý ª« ¥ó ªº ®Ç Ãä «Ø ¥ß €@ ­Ó ·s ª« ¥ó¡A ³o ¹ï ©ó «Ø ¥ß €@ ­Ó ·s ªº ¬Û Šü ª« ¥ó ±N ¬O €Q €À €è «K ªº ¡C µM «á »Ý ­n šê ·s pgAdmin ŸÉ Äý Ÿ¹ Åã ¥Ü ·s «Ø ª« ¥ó ¡C +

+ +

+¥i ¥H §Q ¥Î ³o ­Ó €â ¬q °õ Šæ €£ ŠP ª« ¥ó €W ªº ŠU ºØ ŸÞ §@¡A +µM ŠÓ PostgreSQL ªº CREATE OR REPLACE »y ªk ¹ï ©ó œs ¿è µø Æ[ ªí¡B ¹w Àx µ{ §Ç ©M šç ŒÆ ªº ©w žq €Ž µM ¯S §O Š³ ¥Î¡C +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/autovacuum.html (revision 1448) @@ -0,0 +1,23 @@ + + + + + +Guru Hints + +

±ÀÂ˹BŠæ pg_autovacuum

+

+pg_autovacuum ¥H «e ¬O €@ ­Ó ¥~ ³¡ ªA °È ¶i µ{¡A PostgreSQL 8.1 ¶} ©l €w žg ³Q Ÿã ŠX ¶i žê ®Æ ®w «á ºÝ¡A +¥Š ±N Šb ³Q ­× §ï ªº žê ®Æ Á` ŒÆ ¹F šì «ü ©w ­È ¥H «á ŠÛ °Ê ¹B Šæ VACUUM¡C +

+

+Šb PostgreSQL Šø ªA Ÿ¹ €W ¹B Šæ VACUUM «O «ù žê ®Æ §¹ Ÿã ©M Šø ªA Ÿ¹ ®Ä ²v ¬O ±j šî ­n šD¡A +±À ÂË ³q ¹L Šb postgresql.conf €å ¥ó €€ ³] žm 'autovacuum'¡B'stats_start_collector' ©M 'stats_row_level' °Ñ ŒÆ ¬° 'on' šÓ ¶} ±Ò pg_autovacuum Šu Å@ µ{ §Ç¡C +°l ÂÜ žê ®Æ ÅÜ €Æ ®É ¹ï ©Ê ¯à ·| Š³ »Ž ·L ªº Œv ÅT¡A Šý ¬O ŽN Á` Åé šÓ Á¿¡A ±z ±N ±q ŠÛ °Ê ¹B Šæ VACUUM €€ Àò ±o §ó Šh ¯q ³B¡C +

+

+ +¬° ¯S ®í »Ý šD œÕ Ÿã pg_autovacuum ªº °õ Šæ¡A ¥i ¥H ­× §ï postgresql.conf ªº ¥þ §œ °Ñ ŒÆ ©Î ªÌ ¬Y ­Ó žê ®Æ ªí ªº ­Ó §O ³] žm¡A œÐ °Ñ Ÿ\ €å ÀÉ¡C +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/conn-listen.html (revision 1448) @@ -0,0 +1,42 @@ + + + + + +Guru Hints + + + + +

ŠøªAŸ¹šSŠ³¶iŠæºÊÅ¥

+

+Šø ªA Ÿ¹ µL ªk ±µ šü ³s œu¡G ¥Ñ ³s œu žê ®Æ ®w ³ø §i +

+

+ +

+

+ +Šp ªG ¬Ý šì ³o ­Ó ®ø ®§¡A œÐ ÀË ¬d ¥¿ Šb žÕ ¹Ï ³s ±µ ªº Šø ªA Ÿ¹ ¬O §_ Šb «ü ©w ºÝ €f €U ¹B Šæ PostgreSQL¡A +šÏ ¥Î ping ©Î ªÌ ¬Û Šü €u šã ÀË ¬d «È €á ºÝ šì Šø ªA Ÿ¹ ¥D Ÿ÷ €§ ¶¡ ¬O §_ Šs Šb ºô µž ³s ±µ¡A +§A ªº ºô µž / VPN / SSH ³q ¹D / šŸ €õ Àð ¬O §_ ¥¿ œT ³] žm¡C +

+

+¥X ©ó Šw ¥þ ­ì Š]¡A PostgreSQL ³Ì ªì €£ ·| ºÊ Å¥ Šø ªA Ÿ¹ ªº ©Ò Š³ Š³ ®Ä IP Ša §}¡A +¬° €F ¯à °÷ ³q ¹L ºô µž ³s ±µ žê ®Æ ®w¡A ­º ¥ý »Ý ­n ³] žm ¥Š ¯à °÷ ºÊ Å¥ ¬Û ¹ï À³ ªº Ša §}¡C +

+

+±q PostgreSQL 8.0 ¶} ©l¡A ¥i ¥H Šb postgresql.conf €å ¥ó €€ ¥Î "listen_addresses" °Ñ ŒÆ ±± šî ºÊ Å¥¡C +¥i ¥H Šb ³o žÌ ¿é €J €@ ­Ó À³ žÓ ³Q ºÊ Å¥ ªº IP Ša §} ŠC ªí¡A ©Î ªÌ ¥Î '*' ªí ¥Ü ºÊ Å¥ ©Ò Š³ Š³ ®Ä Ša §}¡C +¹ï ©ó €ñ žû Š­ ªº ª© ¥» ¡]7.3 ©Î ªÌ 7.4¡^¡A »Ý ­n ±N "tcpip_socket" °Ñ ŒÆ ³] žm ¬° 'true'¡C +

+

+¥i ¥H šÏ ¥Î Šb pgAdmin III €€ Ÿã ŠX ªº postgresql.conf œs ¿è Ÿ¹ šÓ œs ¿è postgresql.conf °t žm €å ¥ó¡A +­× §ï ³o ­Ó €å ¥ó €§ «á¡A »Ý ­n ­« ·s ±Ò °Ê žê ®Æ ®w ¶i µ{ šÏ ³] žm Š³ ®Ä¡C +

+

+Šp ªG Šh Šž ÀË ¬d °t žm €§ «á €Ž µM ±o šì ³o ­Ó ¿ù »~ °T ®§¡A ¥i ¯à ¬O ¹J šì €F €@ ­Ó ­P ©R ªº PostgreSQL ¿ù »~¡A +©Î ªÌ ¥i ¯à ¬O §C Œh ºô µž ³s ±µ °Ý ÃD ¡]€ñ Šp šŸ €õ À𠪺 ³] žm¡^¡A Šb ŠV PostgreSQL ¹Î ¶€ Ž£ ¥æ bug ³ø §i €§ «e œÐ ¥J ²Ó ÀË ¬d¡C +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/fki.html (revision 1448) @@ -0,0 +1,33 @@ + + + + + +Guru Hints + + + +

¥~³¡Áä(FK)¥H€Î¥Šªº¯Á€Þ

+

+¥~ ³¡ Áä ³Q ¥Î šÓ šÏ ¥Î ÅÞ ¿è €è Š¡ Ãö Áp šâ ­Ó žê ®Æ ªí¡A ¬I ¥[ µ¹ ¥Š ­Ì ­­ šî žê ®Æ ÅÜ €Æ¡C +

+

+³o €@ €Á ¶} ©l ©ó ¥D žê ®Æ ªí ¡A ¥Š §@ ¬° ³Q °Ñ ·Ó ªí¡A »Ý ­n Š³ €@ ­Ó ¥D Áä ¡]·í µM¡A ¹ê »Ú €W ³Q °Ñ ·Ó ŠC ¥u ­n «D ªÅ šÃ ¥B Š³ °ß €@ ¯Á €Þ €] ¬O ¥i ¥H ªº¡A Šý ¬O šÏ ¥Î ¥D Áä €Ž µM ¬O žû Šn ªº €è Š¡¡^¡C +±q ªí šÌ ¿à ©ó ¥D ªí¡A §ó ·s ©M Ž¡ €J ®É ŸÖ Š³ ¥~ ³¡ Áä ªº Äæ Šì žê ®Æ ¥² ¶· ²Å ŠX ¥D ªí ªº žê ®Æ ¡A ±q ªí ¬O ¥~ ³¡ Áä ªº °Ñ ·Ó ªí ¡C +

+

+¥~ ³¡ Áä €£ ¶È ­­ šî °Ñ ·Ó ªí ¡A €] ­­ šî ³Q °Ñ ·Ó ªí ¡A ­­ šî €è Š¡ ¥i ¥H ¬O RESTRICT¡B CASCADE ©Î SET NULL ¡C +³o ·N šý µÛ¡A ·í ³Q °Ñ ·Ó ªí žê ®Æ µo ¥Í ÅÜ €Æ ¡]§ó ·s ©Î §R °£¡^ ®É¡A ©Ò Š³ ªº °Ñ ·Ó ªí ³£ ·| ÀË ¬d žê ®Æ ¬O §_ ŠX ²z ¡A ¥H €Î ¬O §_ »Ý ­n šä ¥L ªþ ¥[ ŸÞ §@¡C +¬d Ÿ\ PostgreSQL Ãö ©ó ¥~ Áä ªº €å ÀÉ ¥i ¥H §ä šì §ó Šh ²Ó ž` ¡C + +

+

+³Q °Ñ ·Ó ªí ªº ¯S ©w Šæ žê ®Æ µo ¥Í ÅÜ €Æ ®É ¡A ©Ò Š³ ¬Û Ãö ªº °Ñ ·Ó ªí ³£ ·| šÏ ¥Î ¥~ Áä Šr ¬q §@ ¬° ±ø ¥ó °õ Šæ ¬Û À³ ªº Ū ŸÞ §@ ¡C +Š] Š¹ ¡A ©Ò Š³ Ž£ °ª Ū šú ®Ä ²v ªº ³] ­p ­ì «h €] ŸA ¥Î ©ó °Ñ ·Ó ªí Šr ¬q ¡C ¬° €F Š³ š} Šn ªº °õ Šæ ®Ä ²v¡A €j Šh ŒÆ ±¡ ªp €U «Ø ¥ß ¯Á €Þ ¬O ©ú ŽŒ ªº ¿ï ŸÜ ¡C +PostgreSQL šÃ šS Š³ ±j ­¢ ³o ŒË °µ¡A »Ý ­n žê ®Æ ®w ³] ­p €H ­û šÓ Ž£ šÑ ŠX ²z ªº ¯Á €Þ ¡C +

+

+¬° €F €è «K ¡A pgAdmin III Šb ³Ð «Ø ¥~ ³¡ Áä ®É Ž£ šÑ €@ ­Ó ² «K ªº checkbox ¡A ŠÛ °Ê ÀË ¬d ¬O §_ Š³ ŠX ²z ªº ¯Á €Þ Šs Šb ¡A Šp ªG šS Š³ «h «Ø ¥ß €@ ­Ó ¡C +Šp ŠP ©Ò Š³ šä ¥Š ¯Á €Þ €@ ŒË ¡A Š³ ·¥ €Ö ŒÆ ªº ±¡ ªp €Ï ŠÓ ­° §C Á` Åé °õ Šæ ®Ä ²v ¡A Á` ±o šÓ »¡ ¡A ¯Á €Þ €Ó €Ö €ñ ¯Á €Þ €Ó Šh ¹ï ©Ê ¯à ªº Œv ÅT §ó €j ¡C +

+ Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,20 @@ + + + + + +Guru Hints + + + + +

Win32 ŠøªAŸ¹€§€Wªº Unicode œsœX

+

+žê ®Æ ®w šÏ ¥Î Unicode¡]UTF8¡^ œs œX šÓ «O Šs ©M ŸÞ §@ ¹B Šæ ©ó Win32 Šø ªA Ÿ¹ €§ €W ªº PostgreSQL 8.0 Šø ªA Ÿ¹ žê ®Æ ¡C

+

+Š] ¬° §@ ·~ št ²Î šS Š³ Ž£ šÑ š¬ °÷ ªº €ä «ù ¡A Win32 €§ €U ªº PostgreSQL 8.0 µL ªk šÌ ŸÚ ŸA ·í ªº Šž §Ç ¹ï Šr ²Å Šê ¶i Šæ ±Æ §Ç ¡C

+

+ +°w ¹ï ·í «e Šw žË ¡A ±À ÂË šÏ ¥Î ¥» Ša €Æ œs œX ¡B Šb €£ ŠP §@ ·~ št ²Î €§ €W ¹B Šæ ©Î ªÌ ±N žê ®Æ ®w €É ¯Å šì Š³ ±M ªù ¥N œX ¥i ¥H €ä «ù Unicode ±Æ §Ç ªº PostgreSQL 8.1 ¡C

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/pk.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Guru Hints + + + + +

¥DÁä(PK)

+

+·í ³] ­p žê ®Æ ªí ªº ®É ­Ô¡A ¥² ¶· ®É šè Ãö ª` €µ «á Šp Šó Šb ªí €€ ©w Šì žê ®Æ €j Šh ŒÆ ±¡ ªp €U¡A »Ý ­n ¥Î €@ ­Ó ŒÐ ÃÑ ²Å °ß €@ ©Ê Ša ©w Šì €@ Šæ žê ®Æ¡A ³o ­Ó ŒÐ ÃÑ ²Å À³ žÓ §@ ¬° ¥D Áä ³B ²z¡C ¥D Áä €£ ¥² ¥u ¥] §t ³æ €@ ªº Äæ Šì¡A ¥i ¥H ¥] §t Šh ­Ó ¥² »Ý Äæ Šì ¥Î šÓ ŒÐ ÃÑ ¬Y Šæ žê ®Æ¡C Šp ªG »Ý ­n ¥Î Šh ­Ó Äæ Šì ¡]®Ú ŸÚ žg Åç ¡G €j ©ó 3¡^ «Ø ¥ß ¥D Áä¡A ŒW ¥[ €@ ­Ó ±Ä ¥Î §ó ¥[ €è «K Ãþ «¬ ¡]€ñ Šp ¡G serial ©Î ªÌ bigserial¡^ ªº Äæ Šì §@ ¬° ¥D Áä ¥i ¯à ¬O ­Ó Šn ¥D ·N¡C

+

+¥u Š³ ·¥ €Ö ŒÆ ±¡ ªp €U¡A ¥D Áä €~ ¬O µL Ãö ºò ­n ªº¡C ³o ·N šý µÛ¡G €@ ­Ó ¿ò ¥¢ ªº ¥D Áä ±j ¯P ·t ¥Ü µÛ ³o ­Ó žê ®Æ ªí šS Š³ §¹ ¥þ ³] ­p §¹ ²Š¡C ³o €] ¬O ¬° €° »ò Guru Hint ·| Šb ³Ð «Ø šS Š³ ¥D Áä ªº ªí ®É Ž£ ¥Ü §A ªº ­ì Š]¡C

+

+ +Šp ªG §A ¬d ¬Ý PostgreSQL ªº št ²Î ªí¡A ·| µo ²{ ¥Š ­Ì ³£ šS Š³ ¥D Áä¡A ¬° €° »ò ·| ³o ŒË¡H ¹ê »Ú €W¡A ©Ò Š³ ³o šÇ ªí ³£ Š³ €@ ­Ó ©Î ªÌ šâ ­Ó €£ €¹ ³\ ¬° 0¡B ¯à °÷ ³Q ¯Á €Þ §Ö ³t ³X °Ý¡B ¯à °÷ °ß €@ ŒÐ ÃÑ šC €@ Šæ ªº Äæ Šì ¡]³q ±` ¥u Š³ OID¡^¡A ¿í Ž` ¥D Áä ªº ²Ä €G ­Ó ­ì «h ¡C Šb ³o žÌ šÏ ¥Î OID Š³ Ÿú ¥v ©Ê ­ì Š]¡A ¥Š €£ ¬O ³] ­p ¥Î €á ªí ªº ²Ä €@ ¿ï ŸÜ ¡C Áö µM Š³ Åã Š¡ ¥D Áä ³o ºØ §ó ·s §ó ŠX ŸA ªº €è Š¡¡APostgreSQL ¬° €F «O «ù š} Šn ªº ŠV «á ­Ý ®e ©Ê €Ž µM šÏ ¥Î  ªº €è Š¡¡C

+

+¥¿ Šp št ²Î ªí ªº šÒ €l ©Ò ¥Ü¡A §Ö ³t ³X °Ý ©M «O «ù °ß €@ ©Ê ªº ¥Ø ŒÐ ¥i ¥H ³q ¹L šä ¥L €è Š¡ ¹F šì¡A ŠÓ €£ ¬O ±Ä ¥Î ¥D Áä¡C Šý ¬O¡A ¬° €F šÏ žê ®Æ ŒÒ «¬ §ó ¥[ ²M Ž·¡A §Ú ­Ì €Ž µM ±j ¯P ±À ÂË šÏ ¥Î ¥D Áä šÓ ¹F Šš ³o €@ ¥Ø ŒÐ¡C

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/saving-passwords.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/saving-passwords.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/saving-passwords.html (revision 1448) @@ -0,0 +1,16 @@ + + + + + +Guru Hints + + +

«OŠs±KœX

+

+ĵ §i¡G ±z €w žg ¿ï ŸÜ €F «O Šs ±K œX¡A Šb *nix €U ¥Š ±N ³Q «O Šs Šb /home ¥Ø ¿ý ªº ¯Â €å ¥» €å ¥ó €€¡A ŠÓ Šb Windows št ²Î €U ¥Š ±N ³Q «O Šs Šb šÏ ¥Î ªÌ ªº °t žm €å ¥ó €€¡C Šp ªG ±z €£ ·Q ³o »ò °µ¡A œÐ ÂI À» [šú ®ø] «ö ¶s¡C

+

+pgAdmin šÏ ¥Î PostgreSQL ªº 'pgpass' Ÿ÷ šî «O Šs ±K œX¡C Šb *nix št ²Î €U¡A ±K œX ±N ³Q «O Šs Šb ~/.pgpass €å ¥ó €€¡F ŠÓ Šb Windows št ²Î €U¡A ¥Š ±N ³Q «O Šs Šb %APPDATA%\PostgreSQL\pgpass.conf €å ¥ó €€ ¡]%APPDATA% ¬O Šì ©ó šÏ ¥Î ªÌ °t žm €å ¥ó €§ €º ªº 'Application Data' €å ¥ó §š¡^¡C ³o ­Ó Ÿ÷ šî ³Q ¥Î šÓ §@ ¬° šÏ ¥Î libpg ®w ³s ±µ žê ®Æ ®w Šø ªA Ÿ¹ ªº ©Ò Š³ µ{ §Ç ªº ¹w ³] Ÿ÷ šî¡A ¥] ¬A ©R ¥O Šæ µ{ §Ç¡]šÒ Šp pg_dump ©M pg_restore¡^¡B šä ¥L GUI µ{ §Ç¡B ÅX °Ê µ{ §Ç ¡]šÒ Šp ¡G psqlODBC¡^¡C ³o ·N šý µÛ ³o šÇ µ{ §Ç ³£ ¥i ¥H šÏ ¥Î ³o ­Ó «O Šs ªº ±K œX ŠÛ °Ê ³s ±µ šì žê ®Æ ®w¡A Šp ªG §A €£ ·Q ³o ŒË °µ¡A €£ ­n šÏ ¥Î pgAdmin ªº Store Password ªº ¿ï ¶µ¡C

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/hints/multiple.html (revision 1448) @@ -0,0 +1,12 @@ + + + + + +Guru Hints + + +

+pgAdmin III µo ²{ ·í «e ª« ¥ó Š³ Šh ­Ó «Ø ij¡C

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/zh_TW/tips.txt (revision 1448) @@ -0,0 +1,84 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +PostgreSQL 的執行效胜可以通過定期對資料庫進行空間回收(VACUUM)埗到提高。 +PostgreSQL 官方生日是 7月8日專案開始斌 1996幎。 +原始 pgAdmin 專案的第䞀個原型叫做 pgManager是為 PostgreSQL 6.3.2 線寫的。 +pgAdmin 的技術支持可以通過郵件列衚 pgadmin-support@postgresql.org 獲埗。 +pgAdmin 的開癌成員們通過郵件列衚 pgadmin-hackers@postgresql.org èšŽè«–æ–°ç‰¹æ€§å’Œé–‹ç™Œæƒ +況。 +pgAdmin II 䜿甚的 pgSchema 庫倧郚分是圚牛接附近的䞀台電芖機前甚 Windows 2000 筆蚘本開癌的。 +可以䜿甚 [檔案] 遞單裡的 [曎改密碌] 䟆修改密碌。 +SQL 窗栌顯瀺遞取物件的反向工皋 SQL 語句。 +42 是生呜、宇宙和萬物的終極解答。 +pgAdmin 的開癌人員分䜈圚英國、法國、執國、意倧利和矎國。 +為了枛少 OID 的䜿甚埞 PostgreSQL 7.2 開始支持沒有 OID 列的衚。 +䜿甚 [å·¥å +·]->[䌺服噚狀æ +‹] 可以監芖每䞀個基斌連線為單䜍的系統掻動。 +圚源代碌暹的 /contrib 目錄䞋有蚱倚有甚的文件、工å +·å’Œæ–¹æ¡ˆã€‚ +PostgreSQL çš„å­˜å„²éŽçš‹èªžèš€åŒ +括pl/pgSQL、pl/Python、pl/TCL、pl/Perl 和 pl/sh。 +pgAdmin II 圚第䞀個å +·æœ‰æ­£åŒç‰ˆå“è³ªçš„版本癌䜈*以前*å°±æœ‰è¶ +過 10,000次的䞋茉。 +pgAdmin II 第䞀個穩定版本圚它癌䜈埌的 6個月之å +§è¢«äž‹èŒ‰è¶ +過 35,000次。 +䟆自 www.slony.info 的 Slony-I 專案可以甚䟆做䞻埞匏資料庫耇寫系統。 +pgAdmin II 的第䞀個官方穩定版本是圚 2002幎1月16日癌䜈的。 +pgAdmin III 專案的開癌開始斌 2002幎9月29日。 +pgAdmin III 是䞀個基斌 wxWidgets 開癌框架䜿甚 C++ 線寫的å +šæ–°ç‰ˆæœ¬ïŒŒå¯ä»¥é‹è¡Œåœš Windows 和 *nix 系統之䞊。 +pgAdmin 是基斌開攟源碌的'Artistic協議'癌䜈的。 +PostgreSQL 7.3 可以支持架構暡匏(schema)它是資料庫之å +§çš„獚立呜名空間。 +å +±åŒå€ŒåŸŸ(Domains)可以甚䟆創建圚倚敞個䞀般基本類型䞊的預å +ˆå®šçŸ©å +±åŒé¡žåž‹ã€‚ +pgAdmin III 1.0.0 正匏版本圚 2003幎9月26日癌䜈。 +劂果悚的加å +¥æ¬„䜍的資料類型䞍笊合PostgreSQL 的 planner 將跳過指定的玢匕掃瞄。 +䞍芁䜿甚 'kill -9' 呜什關閉 postmaster 進皋 !!! +優化 SQL 查詢時「EXPLAIN ANALYZE」呜什和 [解釋分析查詢] 按鈕是䜠的奜朋友。 +PostgreSQL 8.0 å¢žåŠ çš„äž»èŠæ–°ç‰¹æ€§ïŒŒåŒ +括儲存點(Savepoints)ã€è¡šç©ºé–“ïŒŒä»¥åŠå€§å®¶é•·ä¹ +ç­‰åŸ +的 Windows 版本。 +pgAdmin III 支持 SSL 加密連接。 +新的 Win32 版 PostgreSQL 第䞀次通過它的回歞枬詊是圚 2004幎10月24日。 +Windows 版 PostgreSQL 圚它最初癌䜈的 5倩之å +§è¢«äž‹èŒ‰è¶ +過 45,000次。 +「絊目前還沒有創建的物件蚭眮 ACL 時沒有䜿[ok]按鈕有效」的 bug 是圚芬蘭䞊空 39,000 英呎的地方由 Andreas、Magnus 和 Dave 修正的當時他們正圚埞日本的 Slony-I 和 pgAdmin III 展瀺會返回途䞭。 +為 PostgreSQL 蚭眮過倚的å +±äº«å¿«å–可胜絊執行效率垶䟆負面圱響因為它盞對枛少了䜜業系統栞心檔案緩衝空間的可甚蚘憶體。 +持續坐 12小時板凳真地會什人厭ç +©è€Œäž”é ­è +Šéº»æœšïŒŒé€™å°±æ˜¯ç‚ºä»€éºŒæˆ‘珟圚寫新小秘蚣的原因。 +日本 PostgreSQL äœ¿ç”šè€ +團體JPUGïŒ‰å·²ç¶“æœ‰è¶ +過 5000 的成員䞊䞔還圚持續增長。 +pgAdmin 1.4 èˆ‡ä»¥å‰çš„ç‰ˆæœ¬ç›žæ¯”æ”¯æŒæ›Žå€šçš„å¹³å°ïŒŒåŒ +括真倚 Linux 版本、Microsoft Windows(tm)、FreeBSD、Solaris和Mac OS X。 +pgAdmin 1.4 åŒ +含了䞀個圖圢化的 [解釋分析(EXPLAIN)å·¥å +·]可以甚䟆曎容易地閱讀和理解查詢蚈劃。 +pgAgent 可以甚䟆做為有芏埋執行的批次處理和 SQL äœœæ¥­åˆ¶å®šèšˆåŠƒè¡šïŒŒäŸ‹åŠ‚é‡å»ºè³‡æ–™æ•æ„Ÿçš„å±€éƒšçŽ¢åŒ•ã€èˆŠçŽ€éŒ„çš„æž +陀。 +äœ¿ç”šå‡œæ•žæˆ–è€ +芖觀衚將應甚皋序邏茯攟進資料庫是䞀個奜的習æ +£ïŒŒé€™æš£èƒœå€ ç¢ºä¿ç”¢å“çš„䞍同客戶端瞜是看到盞同的資料芖圖䞊䞔瞜是䜿甚盞同的邏茯䟆曎新資料。劂果䞍這暣做䜠䞍埗䞍把邏茯圚每䞀個客戶端䞊寊珟䞀次。 +為了提高資料庫的安å +šæ€§ïŒŒå‰µå»º pg_hba.conf 時最小化可以蚪問資料庫的遠端䞻機的敞量䞊䞔瞜是䜿甚加密連接陀非䜠有曎奜的理由䞍這暣做。 +å¯ä»¥é€šéŽæ‹’çµ•äž€å€‹äœ¿ç”šè€ +æˆ–è€ +çŸ€çµ„èšªå•æŸå€‹è³‡æ–™è¡šïŒŒè€Œå»ºç«‹äž€å€‹å®ƒå¯ä»¥èšªå•çš„åªåŒ +å«å®ƒæ‡‰è©²çœ‹åˆ°æ¬„äœçš„èŠ–è§€è¡šäŸ†é™åˆ¶äœ¿ç”šè€ +æˆ–è€ +çŸ€çµ„èšªå•ç‰¹å®šæ¬„äœã€‚åŠ‚æžœäœ¿ç”šè€ +需芁曎新基衚資料可以創建䞀個將曎新埞芖觀衚應甚到衚䞊的芏則(rules)䟆寊珟。 +PostgreSQL 可以運行圚異皮平台之䞊䟋劂埮軟的 X-Box、玢尌的 PlayStation II 以及倏普的 Zaurus PDA。 +EnterpriseDB 捐莈了䞀台 Apple Powerbook 絊 pgAdmin 專案甚䟆提升 pgAdmin 圚 Mac OS X 系統䞊的品質和他們簡化過的衍生產品EDB Studio。 Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Gurun neuvot + + + + +

Tietokannan merkistö

+

+Tietokanta käyttää SQL_ASCII-merkistöä. SQL_ASCII-merkistö on tarkoitettu vain 7-bittisiä merkkejä varten; merkkien, joiden 8. bitti on asetettu (ASCII-merkistön ulkopuoliset merkit 127-255), merkitystä ei ole määritelty. Tämän takia palvelin ei pysty muuntamaan dataa muihin merkistöihin. +

+

+Jos tallennat mitään muuta kuin ASCII-dataa (esimerkiksi tekstiä jossa on ä- tai ö-kirjaimia), kannattaa valita kunnollinen merkistö joka tukee kaikkia tarvitsemiasi merkkejä, jolloin palvelin pystyy tarvittaessa muuntamaan tekstit asiakasohjelmiston merkistöön. Jos tallennat muuta kuin ASCII-dataa SQL_ASCII tietokantaan, voit törmätä kummallisiin merkkeihin lukiessa tai kirjoittaessa tietokantaan, joka johtuu muunnosongelmista. Se voi aiheuttaa paljon ongelmia kun tietokantaa käytetään eri asiakasohjelmilla ja ajureilla. +

+

+Useimmissa asennuksissa Unicode (UTF8) merkistö on kaikkein joustavin vaihteohto. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-ident.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Gurun neuvot + + + + +

Ident-todentaminen epäonnistui

+

+Palvelin ei hyväksy käyttäjää. Palvelin antoi virheilmoituksen: +

+

+ +

+

+Jos tämä viesti näkyy, koneen osoite / käyttäjä / tietokanta -yhdistelmääsi vastaava pg_hba.conf-rivi on määritelty käyttämään "ident"-todennusta. Joissain distribuutioissa, mm. Debianissa, tämä on oletus. Jotta ident-todennus toimisi, tarvitset lisäasetuksia; ks. lisätietoja PostgreSQL:n ohjeista. Aloittelijoille saattaa olla sopivampaa valita toiden todennysmenetelmä; MD5-salatut salasanat on hyvä valinta. Se valitaan allaolevan kaltaisella pg_hba.conf-rivillä: +

+

+host all all 192.168.0.0/24 md5 +

+

+Tämä esimerkki myöntää pääsyn MD5-salatuilla salasanoilla kaikkiin tietokantoihin kaikille käyttäjille aliverkosta 192.168.0.0/24. +

+

+Voit käyttää pgAdmin III:n sisäänrakennettua pg_hba.conf-editoria sen muokkaamiseen. Muutettuasi pg_hba.conf-tiedostoa, palvelimen asetukset pitää ladata uudestaan pg_ctl-komennolla, tai käynnistämällä PostgreSQL uudestaan. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/vacuum.html (revision 1448) @@ -0,0 +1,24 @@ + + + + + +Gurun neuvot + + + + +

VACUUM-komennon ajaminen on suositeltavaa

+

+Taulun "" arvioitu rivimäärä poikkeaa merkittävästi todellisesta rivimäärästä. Sinun tulisi ajaa VACUUM ANALYZE tälle taululle. +

+Sen sijaan että ajat käsin VACUUM ANALYZE-komennon tälle taululle (voit tehdä sen pgAdmin III huolto-valikosta), kannattaa harkita VACUUM ANALYZEn ajamisen automatisointia, esimerkiksi ajastinohjelmalla. PostgreSQL tarjoaa myös pg_autovacuum-daemonin, joka seuraa tietokantaan tehtyjä muutoksia ja ajaa VACUUM-komennon aina tarvittaessa. Useimmissa tapauksissa pg_autovacuum on paras vaihtoehto. +



+Mihin VACUUMia tarvitaan? +

+PostgreSQL:n optimoija tekee päätöksensä arvioituihin rivimääriin perustuen. Jos arvioitu rivimäärä poikkeaa liian paljon todellisuudesta, optimoija voi tehdä huonon päätöksen, joka johtaa huonoon saantipolkuun ja sitä kautta huonoon suorituskykyyn. +

+PostgreSQL tarvitsee VACUUMia tauluijen transaktio-ID-numeroiden kiinnittämiseksi. VACUUM myös siivoaa rivien poistamisessa ja päivittämisessä syntyviä vanhoja riviversioita, vapauttaen niiden viemän tilan käyttämisen uudelleen. Online-dokumentaatiosssa on paljon yksityiskohtaista tietoa aiheesta; paina vain "Apua"-nappia. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/instrumentation.html (revision 1448) @@ -0,0 +1,33 @@ + + + + + +Gurun neuvot + + + + +

Palvelimen instrumentointi

+

+Palvelimella ei ole instrumentointifunktioita. +

+

+pgAdmin III käyttää eräitä apufunktioita jotka eivät kaikissa PostgreSQL versioissa tule valmiiksi asennettuina. Funktiot mahdollistavat toimintoja jotka helpottavat loki- ja asetustiedostojen hallintaa. +

+

+Asentaessasi PostgreSQL versio 8.0:n tai uudemman Windows-installerilla, sinun tarvitsee vain valita "admin"- tai "adminpack"-moduli. +

+

+Kääntäessäsi lähdekoodista, tarvittavat tiedostot löytyvät pgAdminin lähdekoodipaketin xtra-hakemistosta. Jos käytät PostgreSQL:n versiota 8.0, kopioi admin-alihakemisto PostgreSQL:n contrib-hakemistosta, ja aja "make" ja "make install". Jos käytät PostgreSQL:n versiota 8.1, käytä admin81-hakemistoa admin-hakemiston sijaan. +

+PostgreSQL versiossa 8.2 ja uudemmissa instrumentointifunktiot tulevat asennuspaketin mukana "adminpack" contrib-modulissa. +

+

+Kun moduli on asennettu, instrumentointifunktiot tulee luoda huoltotietokantaan käyttäen admin.sql-skriptiä (admin81.sql PostgreSQL 8.1 versiota varten) joka on yleensä pgsql share-hakemisossa (esim. /usr/local/pgsql/share). +

+

+Laajennettu palvelimen instrumentointi ei ole tuettu versioissa 7.3 ja 7.4. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,19 @@ + + + + + +Gurun neuvot + + + + +

Taulun sisällön muokkaus ilman primääriavainta

+

+Koska taululla ei ole primääriavainta tai OID:ta, voit vain katsella sen sisältöä. Uusien rivien lisäys ja vanhojen muokkaus ei ole mahdollista taulun sisällönmuokkaustyökalulla ilman primääriavainta. +

+

+Voidaksesi muokata sisältöä, pgAdmin III tarvitsee primääriavaimen, joka on hyvä suunnitteluperiaate joka tapauksessa. Vaihtoehtoisesti voit luoda taulun WITH OIDS-optiolla. Huomaa että oid:t eivät ole välttämättä yksilöiviä pitkän ajan kuluessa, joten oid:n käyttö primääriavaimen korvikkeena ei ole ensisijainen vaihtoehto. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-hba.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Gurun neuvot + + + + +

Pääsy tietokantaan evätty

+

+Palvelin ei myönnä pääsyä tietokantaan. Palvelin antoi virheilmoituksen: +

+

+ +

+

+Saadaksesi yhteyden tietokantaan PostgreSQL palvelimella, sinun täytyy ensin +myöntää pääsy palvelimelle käyttämältäsi koneelta (Host Based Authentication). +PostgreSQL tarkastaa pg_hba.conf-tiedostosta täsmääkö mikään rivi sinun koneesi osoitteen / käyttäjätunnuksen / tietokannan kanssa, ennen kuin se tulkitsee SQL +GRANT käyttöoikeuksia. +

+

+pg_hba.conf-tiedoston alkuasetukset ovat varsin rajoittavia, tietoturva-aukkojen välttämiseksi. Haluat todennäköisesti lisätä siihen jotain tämän tapaista: +

+

+host all all 192.168.0.0/24 md5 +

+

+Tämä esimerkki myöntää pääsyn MD5-salatuilla salasanoilla kaikkiin tietokantoihin kaikille käyttäjille aliverkosta 192.168.0.0/24. +

+

+Voit käyttää pgAdmin III:n sisäänrakennettua pg_hba.conf-editoria sen muokkaamiseen. Muutettuasi pg_hba.conf-tiedostoa, palvelimen asetukset pitää ladata uudestaan pg_ctl-komennolla, tai käynnistämällä PostgreSQL uudestaan. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/object-editing.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/object-editing.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/object-editing.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Gurun neuvot + + + + +

Näkymien, talletettujen proseduurien tai funktioiden muokkaus

+

+Muokatessasi näkymän, proseduurin tai funktion lähdekoodia, voit muokata objektia myös kyselytyökalussa käyttäen pgAdminin skriptitoimintoa, ominaisuudet-ikkunan pienen laatikon sijaan. Tämä mahdollistaa kyselytyökalun editorin ominaisuuksien, kuten tab-täydennyksen ja etsi-korvaa-toiminnon käytön, sekä isomman työskentelytilan. +

+ +

+Käyttääksesi skriptitoimintoa, klikkaa objektia pgAdminin puunäkymässä oikealla hiirennapilla, +ja valitse CREATE skripti. Se voi olla Skriptit alivalikossa. Vaihtoehtoisesti +voit valita objektin ja valita sitten CREATE skripti Työkalut-valikon Skriptit-alivalikosta. +

+ +

+Muokkaa objektin luontilausetta tarpeen mukaan, ja käytä Suorita kysely-nappia muutosten +voimaansaattamiseksi. Muista että näkymän tai funktion nimen, tai funktion tai proseduurin +parametrien, muuttaminen voi luoda uuden objektin vanhan rinnalle. Tämä sivuvaikutus on kätevä +kun haluat luoda uuden, mutta samankaltaisen objektin. Voit joutua virkistämään objektien selaus -näytön nähdäksesi uudet objektit. +

+ +

+Voit käyttää tätä tekniikkaa kaikenlaisten operaatioiden suorittamiseksi eri objekteille, mutta +PostgreSQL:n CREATE OR REPLACE syntaksi tekee sen erityisen käteväksi näkymien, proseduurien ja funktioiden kanssa. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/autovacuum.html (revision 1448) @@ -0,0 +1,31 @@ + + + + + +Gurun neuvot + + + + +

pg_autovacuum:n ajaminen on suositeltavaa

+

+PostgreSQL:n 8.1-versiosta lähtien pg_autovacuum, joka oli ennen ulkoinen +ohjelma, on integroitu palvelinohjelmistoon. Se ajaa VACUUM-komennon +automaattisesti kun säädetty määrä dataa on muuttunut. +

+

+VACUUM-komennon ajaminen on pakollista PostgreSQL:ssä datan eheyden ja +palvelimen suorituskyvyn varmistamiseksi. Suosittelemme pg_autovacuumin +kytkemistä päälle asettamalla "autovacuum"-, "stats_start_collector"- ja +"stats_row_level"-asetukset "on"-asentoon postgresql.conf-tiedostossa. +Datan muutosten seuraamisesta aiheutuva rasitus on yleensä merkityksettömän +pieni, ja saat automaattiset, suorituskykyiset VACUUM-ajot. +

+

+Säätääksesi pg_autovacuumin suorituskykyä yksilöllisiin tarpeisiin, voit +säätämään sen asetuksia globaalisti postgresql.conf-tiedostossa, tai +taulukohtaisesti; katso lisätietoja dokumentaatiosta. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/conn-listen.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Gurun neuvot + + + + +

Palvelin ei huoli yhteyksiä

+

+Palvelin ei huoli yhteyksiä. Yhteyskirjasto antoi virheilmoituksen: +

+

+ +

+

+Jos näet tämän viestin, tarkista että palvelimella johon yrität ottaa yhteyttä todella pyörii PostgreSQL annetussa portissa. Kokeile saatko yhteyden palvelimelle käyttäen esimerkiksi ping-ohjelmaa. Onko verkkosi / VPN-yhteytesi / SSH-tunnelisi / palomuurisi oikein konfiguroitu? +

+

+Tietoturvasyistä PostgreSQL ei oletusarvoisesti kuuntele kaikissa palvelimen IP-osoitteissa. Saadaksesi yhteyden palvelimeen verkon yli, PostgreSQL täytyy asettaa kuuntelemaan verkkoadapterin IP-osoitteessa. +

+

+PostgreSQL versiosta 8.0 lähtien, se tehdään "listen_addresses"-asetuksella postgresql.conf-tiedostossa. Voit kirjoittaa listan IP-osoitteista joissa haluat palvelimen kuuntelevan, tai "*" joka tarkoittaa kaikkia saatavilla olevia IP-osoitteita. Aiemmissa palvelinversioissa (7.3 tai 7.4) "tcpip_socket"-asetus täytyy asettaa "true"-asentoon. +

+

+Voit käyttää pgAdmin III:n sisäänrakennettua postgresql.conf-editoria postgresql.conf-tiedoston muokkaukseen. Muokattuasi tiedostoa, joudut käynnistämään PostgreSQL:n uudestaan jotta uudet asetukset astuvat voimaan. +

+

+Jos tarkistit asetukset, mutta saat silti tämän virheilmoituksen, on silti epätodennäköistä että törmäsit bugiin PostgreSQL:ssä. Kyseessä on todennäköisesti jokin alhaisen tason yhteysongelma, esim. virhe palomuurin asetuksissa. Tarkista +verkkoasetuksesi tarkasti ennen kuin teet ilmoituksen bugista PostgreSQL-yhteisölle. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/fki.html (revision 1448) @@ -0,0 +1,28 @@ + + + + + +Gurun neuvot + + + +

Viiteavaimen kattavat indeksit

+

+Viiteavainta käytetään yhdistämään toisiinsa kaksi taulua loogisella tavalla, jarajoittamaan niihin sallittavia muutoksia. +

+

+Kaikki alkaa isätaulusta johon viitataan, eli viitatusta taulusta. Se tarvitsee primääriavaimen (tarkkaan ottaen, viitattujen kenttien tarvitsee vain olla määritelty NOT NULLiksi, ja taululla pitää olla yksilöivä indeksi joka kattaa kentät, mutta on erittäin primääriavaimen määritteleminen on erittäin suositeltavaa). Lapsitaulu riippuu isätaulusta, siten että viiteavaimeen kuuluvien kenttien arvojen on vastattava jokaisella rivillä jonkin isätaulussa olevan rivin arvoja. Lapsitaulu on toiselta nimeltään viiteavaimen viittaava taulu. +

+

+Viiteavain rajoittaa paitsi lapsitaulua, myös isätaulua; rajoituksen tyyppi voi olla RESTRICT, CASCADE tai SET NULL. Tämä tarkoittaa, että kun isätaulun riviä muutetaan (UPDATE tai DELETE), kaikkien lapsitaulujen viite-eheys tarkistetaan. Lue lisää PostgreSQL:n dokumentaatiosta kohdasta "foreign keys". +

+

+Tämä tarkoittaa että kun isätaulun riviä muutetaan, viiteavainta vastaavat rivit haetaan kaikista lapsitauluista viite-eheyden tarkistusta varten. Tämän johdosta kaikki lukutapahtumien suorituskykyyn liittyvät säännöt pätevät yleensä myös lapsitaulun kenttiin. Hyvän suorituskyvyn takaamiseksi lapsitaulun viiteavaimille kannattaa yleensä luoda indeksit. PostgreSQL ei valvo sitä millään tavalla, joten indeksin luominen on tietokannan suunnittelijan vastuulla. +

+

+pgAdmin III tarjoaa yksinkertaisen "rasti ruutuun"-valinnan viiteavaimen luomisessa, joka tarkistaa automaattisesti sopivan indeksi olemassaolon, ja luo indeksin jos sitä ei ole ennestään. Kuten aina indeksien kanssa, joissain harvinaisissa tapauksissa indeksi huonontaa hieman suorituskykyä, mutta yleensä ottaen indeksin puuttuminen huonontaa suorituskykyä paljon enemmän kuin ylimääräisen indeksin olemassaolo. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,22 @@ + + + + + +Gurun neuvot + + + + +

Unicode-merkistö Win32-palvelimella

+

+Tietokanta "" käyttää Unicode (UTF8) merkistöä ja sijaitsee PostgreSQL 8.0 palvelimella Win32-palvelimella. +

+

+PostgreSQL 8.0:n Win32-toteutus ei pysty lajittelemaan merkkijonoja käyttäen oikeita lajittelujärjestyksiä, koska käyttöjärjestelmä ei tarjoa siihen tarvittavaa tukea. +

+

+Tällä palvelimella on suositeltavaa käyttää jotain muuta merkistöä, joka tukee tarvittavia merkkejä, siirtää PostgreSQL-palvelin toiselle käyttöjärjestelmälle, tai päivittää palvelin versioon 8.1 joka sisältää ongelman ratkaisemiseksi enemmän ohjelmakoodia unicode-lajittelujärjestyksiä varten. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/pk.html (revision 1448) @@ -0,0 +1,25 @@ + + + + + +Gurun neuvot + + + + +

Primääriavaimet

+

+Suunnitellessasi taulua, pidä aina mielessä miten taulusta tullaan myöhemmin hakemaan rivejä. Useimmissa tapauksissa tarvitset avaimen voidaksesi hakea ja muuttaa tiettyä riviä yksikäsitteisesti; tämä avain tulisi määritellä taulun primääriavaimeksi. Primääriavain ei välttämättä ole vain yksi kenttä; se voi koostua niin monesta kentästä kuin rivin yksilöimiseen tarvitaan. Jos tarvitset montaa kenttää (nyrkkisääntönä voidaan pitää kolmea), voi olla hyvä idea luoda keinotekoinen avainkenttä kätevällä tietotyppillä, esimerkiksi serial tai bigserial. +

+

+Vain äärimmäisen harvinaisissa tapauksissa ei ole järkevää luoda primääriavainta. Toisin sanoen, primääriavaimen puuttuminen on vahva merkki siitä että taulu ei ole valmiiksi saakka suunniteltu; sen takia tämä Gurun neuvo näytetään aina jos luot taulun ilman primääriavainta. +

+

+Jos katsot PostgreSQL:n järjestelmätauluja, huomaat että millään niistä ei ole primääriavainta. Mistä oikein on kysymys? Itse asiasssa, kaikissa näissä tauluissa on yksi tai kaksi kenttää (useimmiten vain OID), joka yksilöi jokaisen rivin, noudattaa primääriavainten toista sääntöä, eli ei huoli NULLia, ja on indeksoitu hakujen nopeuttamiseksi. OID:den käyttö johtuu historiallisista syistä, eikä ole suositeltavaa sovellustaulujen suunnittelussa. PostgreSQL tukee sitä yhä taaksepäin yhteensopivuuden takaamiseksi. Jos järjestelmätaulut suunniteltaisiin tänä päivänä uudelleen, niissä todennäköisesti käytettäisiin primääriavaimia, mutta sitä ei enää lähdetä muuttamaan. +

+

+Kuten järjestelmätaulujen tapaus osoittaa, yksilöllisyyden ja nopeiden hakujen tavoitteeseen voi päästä muillakin keinoilla kuin primääriavaimilla. Siitä huolimatta, tietomallin selkeyden vuoksi, kannattaa ehdottomasti käyttää primääriavaimia tähän tarkoitukseen. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/saving-passwords.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/saving-passwords.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/saving-passwords.html (revision 1448) @@ -0,0 +1,19 @@ + + + + + +Gurun neuvot + + + + +

Salasanojen tallentaminen

+

+VAROITUS: Olet päättänyt tallentaa salasanan. Se tallennetaan selväkielisenä kotihakemistoosi *nix-järjestelmässä, tai käyttäjän profiiliin Windowsissa. Jos et halua näin tapahtuvan, paina Peruuta-nappia. +

+

+pgAdmin käyttää PostgreSQL:n "pgpass"-mekanismia salasanojen tallentamiseen. *nix-järjestelmässä salasana tallennetaan ~/.pgpass-tiedostoon, ja Windows-järjestelmässä se tallennetaan %APPDATA%\PostgreSQL\pgpass.conf-tiedostoon (%APPDATA% on "Application Data"-kansio käyttäjäprofiilissasi). Tätä mekanismia käyttää oletusarvoisesti kaikki libpq-kirjastoa käyttävät ohjelmat, kuten komentoriviohjelmat kuten pg_dump ja pg_restore, muut GUI-ohjelmat, sekä jotkin ajurit kuten psqlODBC. Se tarkoittaa että myös nämä ohjelmat voivat ottaa automaattisesti yhteyden tietokantaan käyttäen tallentamaasi salasanaa. Jos et halua näin tapahtuvan, älä käytä Salasanojen tallennus-toimintoa pgAdminissa. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Gurun neuvot + + +

+pgAdmin III löysi monta ongelmaa tämänhetkisestä objektista. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fi_FI/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +Voit parantaa PostgreSQL:n suorituskykyÀ ajamalla VACUUM-komentoa sÀÀnnöölisesti. +PostgreSQL:n virallinen syntymÀpÀivÀ on 8. heinÀkuuta. PostgreSQL-projekti syntyi vuonna 1996. +EnsimmÀinen pgAdmin-projektin prototyyppi oli nimeltÀÀn pgManager, ja oli tehty PostgreSQL 6.3.2 versiota varten. +Voit pyytÀÀ apua pgAdminin kÀyttöön postituslistalla pgadmin-support@postgresql.org. +Uusista ominaisuuksista ja pgAdminin kehittÀmisestÀ keskustellaan kehittÀjien kesken pgadmin-hackers@postgresql.org postituslistalla. +Suurin osa pgAdmin II:n kÀyttÀmÀstÀ pgSchema-kirjastosta kehitettiin telkkarin edessö kannettavalla tietokoneella, Windows 2000:lla, Englannissa lÀhellÀ Oxfordia. +Voit vaihtaa salasanasi valitsemalla "Vaihda salasana" "Tiedosto"-valikosta. +MÀÀritelmÀ-nÀyttö nÀyttÀÀ SQL-lauseen jolla valittu objekti voitaisiin luoda. +ElÀmÀn, maailmankaikkeuden ja kaiken vastaus on 42. +pgAdminin ydinkehittÀjiÀ asuu Iso-Britanniassa, Ranskassa, Saksassa, Italiassa ja Yhdysvalloissa. +PostgreSQL 7.2 ja uudemmat tukevat tauluja ilman OID-kenttÀÀ, joka vÀhentÀÀ OID:en kulutusta. +Voit monitoroida jÀrjestelmÀÀ yhteys yhteydeltÀ kÀyttÀen Palvelimen Tila-työkalua. +PostgreSQL:n mukana, /contrib hakemistossa, tulee paljon hyödyllisiÀ tiedostoja, työkaluja ja projekteja. +PostgreSQL:n talletettuja proseduureja voi kirjoittaa mm. seuraavilla kielillÀ: pl/pgSQL, pl/Python, pl/TCL, pl/Perl & pl/sh. +pgAdmin II ladattiin yli 10.000 kertaa *ennen* kuin ensimmÀinen julkaisukelpoinen versio oli saatavilla! +pgAdmin II:n ensimmÀinen vakaa versio ladattiin yli 35.000 kertaa julkaisua seuraavien 6 kuukauden aikana. +Voit kÀyttÀÀ Slony-I projektia (www.slony.info) master-slave replikointiin. +EnsimmÀinen vakaa pgAdmin II versio julkaistiin 16. tammikuuta 2002. +pgAdmin III:n kehitys alkoi 29. syyskuuta 2002. +pgAdmin III on kokonaan uusi pgAdmin-versio, kirjoitettu C++:lla kÀyttÀen wxWidgets-kirjastoa sekÀ Windows- ettÀ *nix alustojen tukemiseksi. +pgAdmin on julkaistu Open Source 'Artistic LisenssillÀ'. +PostgreSQL 7.3 tukee kaavioita, jotka ovat itsenÀisiÀ nimiavaruuksia tietokannan sisÀllÀ. +Voit kÀyttÀÀ arvoalueita omien, geneerisiin perustietotyyppeihin pohjautuvien tietotyyppien luomiseen. +pgAdmin III 1.0.0 paketoitiin julkaisua varten 26. syyskuuta 2003. +PostgreSQL:n optimoija ei vÀlitÀ halustasi kÀyttÀÀ indeksiÀ, jos liitettÀvien kenttien tietotyypit eivÀt tÀsmÀÀ. +ÄlÀ tapa postmasteria 'kill -9'-komennolla! +"EXPLAIN ANALYZE" ja "Saantipolku"-nappi ovat ystÀviÀsi kun optimoit SQL-kyselyjÀ. +PostgreSQL 8.0 toi mukanaan merkittÀviÀ uusia ominaisuuksia, mukaan lukien jatkoaloituskohdat (savepoints), taulualueet, ja kauan odotettu Windows-versio. +pgAdmin III tukee SSL-salattuja yhteyksiÀ. +PostgreSQL:n uusi Win32-kÀÀnnös lÀpÀisi kaikki regressiotestinsÀ ensimmÀisen kerran 24/10/2004. +PostgreSQL:n Windows-versio ladattiin ensimmÀistÀ julkaisua seuraavien viiden pÀivÀn aikana yli 45.000. +Bugi "ÄlÀ aktivoi OK-nappia asetettaessa ACL:ÀÀ vielÀ luomattomilla objekteille" korjattiin yli 11.000 metrin korkeudessa Suomen yllÀ, kun Andread, Magnus ja Dave palasivat Slony-I ja pgAdmin III esityksestÀ Japanista. +Liian suuri PostgreSQL:n "shared_buffers"-asetus voi olla haitallinen suorituskyvylle, koska se vÀhentÀÀ kÀyttöjÀrjestelmÀn vÀlimuistille kÀyttöön jÀÀvÀn muistin mÀÀrÀÀ. +On ÀÀrimmÀisen tylsÀÀ istua lentokoneessa 12 tuntia, jonka takia kirjoitan juuri nyt uusia vinkkejÀ!! +Japanin PostgreSQL kÀyttÀjÀkerholla (JPUG) on yli 5000 jÀsentÀÀ, ja jÀsenmÀÀrÀ kasvaa koko ajan. +pgAdmin 1.4 on tuettu useammalla alustalla kuin mikÀÀn aiempi versio, mukaan lukien moni Linux-distribuutio, Microsoft Windows (tm), FreeBSD, Solaris ja Max OS X. +pgAdmin 1.4 sisÀltÀÀ graafisen saantipolku-työkalun (EXPLAIN), joka auttaa lukemaan ja ymmÀrtÀmÀÀn saantipolkuja entistÀ paremmin. +Voit kÀyttÀÀ pgAgent:ia toistuvien erÀajojen ja SQL-töiden, kuten pÀivÀmÀÀrÀstÀ riippuvien osittaisten indeksien luomiseen, tai vanhojen tietojen poistoon. +On hyvÀ tapa rakentaa sovelluslogiikka tietokantaan itseensÀ kÀyttÀen funktioita ja nÀkymiÀ. TÀmÀ varmistaa ettÀ kaikki dataa kÀyttÀvÀt sovellukset nÀkevÀt datan samalla tavalla, ja muokkaavat sitÀ aina samalla tavalla. SitÀ paitsi, sinun tarvitsee tehdÀ se vain kerran! +PitÀÀksesi tietokantasi suojattuna, rajaa etÀkoneiden pÀÀsy mahdollisimman tiukasti pg_hba.conf-tiedostossa, ja kÀytÀ aina salattuja yhteyksiÀ ellei sinulla ole hyvÀÀ syytÀ olla kÀyttÀmÀttÀ. +Voit rajata pÀÀsyn taulun tiettyihin sarakkeisiin tietylle kÀyttÀjÀlle tai kÀyttÀjÀryhmÀlle estÀmÀllÀ suoran pÀÀsyn siihen, ja antamalla sen sijaan pÀÀsyn nÀkymÀÀn jossa on vain halutut kentÀt. Jos kÀyttÀjien tarvitsee pÀivittÀÀ taulua, voit luoda nÀkymÀÀn pÀivityssÀÀnnöt jotka pÀivittÀvÀt taulua. +PostgreSQL:À on ajettu mitÀ erilaisimmilla alustoilla, kuten Microsoft X Box, Sony PlayStation II, ja Sharp Zaurus PDA! +EnterpriseDB lahjoitti Apple Powerbookin pgAdmin-projektille auttaakseen pgAdminin sekÀ heidÀn yksinkertaistetun johdannaistuotteen, EDB Studion, Mac OS X-version kehitystÀ. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/builddocs.bat =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/builddocs.bat (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/builddocs.bat (revision 1448) @@ -0,0 +1,9 @@ +@echo off + +REM Compile the HTML Help +"%ProgramFiles%\HTML Help Workshop\hhc.exe" ./en_US/pgadmin3.hhp + +REM Regenerate the cache file used by the wx viewer. +"%WXWIN%\utils\hhp2cached\vc_mswu\hhp2cached.exe" ./en_US/pgadmin3.hhp + +EXIT 0 Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,27 @@ + + + + + +Sugerencias de Gurú + + + + +

Codificación de base de datos

+

+La base de datos es creada para almacenar datos usando la codificación SQL_ASCII. Esta codificación está definida +para carácteres de 7 bit solamente; el siginificado de carcarteres con el 8vo bit encendido (caracters no-ASCII 127-255) no esta definido. +En consecuencia, no es posible para el servidor convertir estos datos a otras codificaciones. +

+

+Si usted está almacenando datos no-ASCII en la base de datos, lo instamos enérgicamente a que use una codificacion de base de datos adecuada representando su conjunto local de caracteres para aprovechar los beneficios de la conversión automática a diferentes codificaciones de clientes cuando sea necesario. +Si almacena datos no-ASCII en una base de datos SQL_ASCII, puede encontrar +caracteres extraños escritos o leídos de la base de datos, causados por problemas de conversion de codificación. +Esto puede causarle muchos dolores de cabeza al acceder a la base de datos usando diferentes programas clientes y manejadores. +

+

+Para la mayoría de las instalaciones, la codificación Unicode (UTF8) proveerá la mayor flexilibilidad. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-ident.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + +Sugerencias de Gurú + + + + +

Autenticación de Ident falló

+

+El servidor no acepta el usuario actual. El servidor reporta +

+

+ +

+

+Si este mensaje aparece, la línea del archivo pg_hba.conf encontrada para la combinación de su cliente / usuario / base de datos +está configurada para autenticación "ident". Algunas distribuciones, p.e. Debian, tiene esto por defecto. +Para realizar autenticación basada en ident exitosamente, necesita configuración adicional; vea la ayuda de PostgreSQL +para ello. Para un principiante, peude ser más apropiado usar un método de autenticación diferente; +contraseñas encriptadas con MD5 son una buena opción, las cuales pueden ser configurdas mediante una entrada en pg_hba.conf como esta: +

+

+host all all 192.168.0.0/24 md5 +

+

+Este ejemplo otorga acceso a través de contraseñas encriptadas MD5 a todas las bases de datos y todos los usuarios en la red privada 192.168.0.0/24. +

+

+Usted puede utilizar el editor de pg_hba.conf que está incluido en pgAdmin III para editar el archivo de configuración pg_hba.conf. +Luego de modificar pg_hba.conf, necesita disparar una recarga de la configuración del servidor utilizando pg_ctl o deteniendo y reiniciando el proceso de servidor. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/vacuum.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + +Sugerencias de Gurú + + + + +

Se recomienda ejecutar VACUUM

+

+El número de filas estimado de la tabla "" difiere significativamente del conteo real. +Usted debería ejecutar VACUUM ANALYZE en esta tabla. +

+En vez de lanzar un comando VACUUM ANALYZE manualmente en esta tabla (puede usar +el menú de mantenimiento de pgAdmin III para ello), debería considerar ejecutar VACUUM ANALYZE en forma regular +o automática. Esto puede ser logrado utilizando un scheduler. PostgreSQL también provee +el demonio pg_autovacuum, el cual hará el seguimiento de los cambios realizados en la base de datos +y lanzará comandos vacuum automáticamente cuando sea requerido. En la mayoría de los casos, pg_autovacuum será la +mejor opción. +



+¿Para qué es bueno VACUUM? +

+El planificador de consultas de PostgreSQL toma sus decisiones basado en suposiciones, tomadas de +los conteos estimados de filas. Si el conteo real de filas es muy diferente del conteo estimado, +el planificador puede tomar una decisión incorrecta, resultando en un plan de consulta que no es óptimo. Esto puede +resultar en pobres prestaciones. +

+El almacenamiento PostgreSQL necesita VACUUM para corregir los ID de transacciones en tablas. +Adicionalmente, filas desactualizadas por actualizaciones y eliminaciones no son limpiadas hasta que se lance +un comando VACUUM en esa tabla. Información detallada puede ser encontrada en la documentación en línea, sólo presione +el botón de ayuda. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/instrumentation.html (revision 1448) @@ -0,0 +1,37 @@ + + + + + +Sugerencias de Gurú + + + + +

Instrumentación del servidor

+

+El servidor carece de funciones de instrumentación. +

+

+pgAdmin III usa alguna funciones de soporte que no están disponibles por defecto +en todas las versiones de PostgreSQL. Éstas habilitan algunas tareas que hacen la vida más fácil al +tratar con archivos de registros (log) y de configuración.. +

+

+Al instalar PostgreSQL 8.0 o superior usando el instalador Windows, sólo necesita +marcar la opción "admin option". +

+

+Al compilar desde los fuentes, los archivos necesarios pueden ser encontrados en el subdirectorio xtra +del árbol de fuentes de pgAdmin. Para PostgreSQL 8.0, copie el directorio admin al + directorio contrib de los fuentes de postgresql, y ejecute make y make install desde allí. Para PostgreSQL 8.1, +use el directorio admin81 para ello. +Después que el módulo está instalado, necesita crear las funciones de instrumentación en +su base de datos de mantenimiento usando el script admin.sql (admin81.sql para PostgreSQL 8.1) +que están usualmente ubicados en el directorio share de pgsql (p.e. /usr/local/pgsql/share) +

+

+La instrumentación extendida de servidor no está soportada para PostgreSQL 7.3 y 7.4. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,21 @@ + + + + + +Sugerencias de Gurú + + + + +

Editar datos de tabla sin clave primaria

+

+Dado que la tabla no tiene una clave primaria o OID, usted sólo puede ver los datos. +Sin clave primaria, no es posible insertar nuevas filas o modificar filas existentes con la herramienta de Edición de Datos. +

+

+Para editar datos, pgAdmin III requiere una clave primaria en la tabla, lo cual es una buena práctica de diseño de bases de datos de todos modos. +Alternativamente, la tabla puede ser creada WITH OIDS. Por favor tome nota que no se garantiza que los oids sean únicos durante un período de tiempo muy largo, por lo que usar oids como un sustituto de clave primaria es sólo una segunda opción. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-hba.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Sugerencias de Gurú + + + + +

Acceso a base de datos denegado

+

+El servidor no permite el acceso a la base de datos: el servidor reporta +

+

+ +

+

+Para acceder a una base de datos en un servidor PostgreSQL, debe primero obtener acceso primario al servidor para su cliente (Autenticación Basada en Host). PostgreSQL verificará en el archivo pg_hba.conf si hay un patrón que +coincida con la dirección / nombre de usuario / base de datos del cliente y que esté habilitado antes que se evalúen la listas de control de acceso SQL GRANT. +

+

+La configuración inicial en pg_hba.conf es bastante restrictiva, de modo tal de evitar agujeros de seguridad no deseados causados por configuraciones obligatorias y no revisadas. Usted probablemente desee agregar algo como +

+

+host all all 192.168.0.0/24 md5 +

+

+Este ejemplo configura el acceso con contraseñas encriptadas MD5 a todas las bases de datos, para todos los usuarios en la red privada 192.168.0.0/24. +

+

+Puede utilizar el editor de pg_hba.conf que estáincluidoo en pgAdmin III para modificar el archivo de configuración pg_hba.conf . Luego de modificar pg_hba.conf, necesita forzar una recarga de la configuración del servidor usando pg_ctl o deteniendo y reiniciando el proceso del servidor. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/object-editing.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/object-editing.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/object-editing.html (revision 1448) @@ -0,0 +1,46 @@ + + + + + + + +Guru Hints + + + + +

Editando Vistas, Procedimientos Almacenados o Funciones

+

+Al editar el código de una vista, procedimiento almacenado o función, en vez de usar el pequeño +cuadro de texto en el diálogo de propiedades del objeto, puede encontrar más conveniente usar +las opciones de scripting en pgAdmin para editar el objeto en la herramienta de consultas. Esto +le da el beneficio de las características del editor de la Herramienta de Consultas tales como +autocompletado, buscar y reemplazar y una mayor área de trabajo. +

+ +

+Para usar las opciones de scripting, en la ventana de explorador de pgAdmin, haga click-botón-derecho +sobre el objeto que desea editar, y seleccione la opción sentencia CREATE. Puede estar en el +submenu Scripts. Alternativamente, puede seleccionar el objeto y luego elegir la opción setencia CREATE +del submenú Scripts del menú Herramientas. +

+ +

+Edite la definición del objeto como se requiera, y +use el botón Ejecutar Consulta para aplicar sus cambios. No olvide que modificar el nombre de +una vista o función, o la firma de una función o procedimiento puede provocar que se cree un nuevo +objeto diferente del original. Este útil efecto colateral lo hace conveniente para crear +objetos nuevos similares a otros. Puede necesitar refrescar el explorador de pgAdmin para mostrar +los nuevos objetos creados. +

+ +

+Usted puede utilizar esta técnica para realizar todo tipo de operaciones en diferentes objetos, +sin embargo la sintaxis CREATE OR REPLACE de PostgreSQL la hace particularmente útil para editar vistas, +procedimientos almacenados y funciones. +

+ + + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/autovacuum.html (revision 1448) @@ -0,0 +1,30 @@ + + + + + +Sugerencias de Gurú + + + + +

Se recomienda ejecutar pg_autovacuum

+

+Introducido en PostgreSQL 8.1, el proceso pg_autovacuum que fue implementado previamente +como un proceso de servicio externo está ahora integrado en el servidor. Ejecutará +VACUUM automáticamente si ha cambiado una cantidad configurable de datos. +

+

+Ejecutar VACUUM es obligatorio en un servidor PostgreSQL para mantener los datos consistentes +y el servidor con buenas prestaciones. Como un comienzo, se recomienda habilitar el demonio +pg_autovacuum estableciendo 'autovacuum', 'stats_start_collector' y 'stats_row_level' +en postgresql.conf como 'on'. Con penalidad de performance por el seguimiento de los cambios de datos, +usualmente imperceptible, ganará ejecuciones automáticas de VACUUM. +

+

+Para ajustar la performance de pg_autovacuum a necesidades individuales, puede necesitar ajustar +su configuración usando parámetros globales en postgresql.conf, o individualmente en cada tabla; vea +la documentación. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/conn-listen.html (revision 1448) @@ -0,0 +1,44 @@ + + + + + +Sugerencias de Gurú + + + + +

El servidor no escucha

+

+El servidor no acepta conexiones: la librería de conexión reporta +

+

+ +

+

+Si usted encuentra esta mensaje, por favor verifique si el servidor que está tratando de contactar esta realmente +ejecutando PostgreSQL el el puerto indicado. Verifique si tiene conectividad de red desde su cliente +al servidor usando ping herramientas equivalentes. ¿ Está su red / VPN / túnel SSH / +cortafuegos configurado correctamente? +

+

+Por razones de seguridad, PostgreSQL no escucha en todas las direcciones IP disponibles en la máquina del servidor inicialmente. Para acceder al servidor desde la red, +usted necesita primero habilitar la escucha en la dirección. +

+

+Para los servidores PostgreSQL comenzando con la versión 8.0, esto +es controlado utilizando el parámentro "listen_addresses" en el archivo postgresql.conf. Aquí, usted puede sepecificar una lista de direcciones IP donde el servidor debe escuchar +, o simplemente usar '*' para escuchar en todas las direcciones IP disponibles. Para servidores anteriores (Versión 7.3 o 7.4), usted necesitará configurar el parámetro "tcpip_socket" como 'true'. +

+

+Usted puede utilizar el editor de postgresql.conf editor incluido en pgAdmin III para editar el archivo de configuración postgresql.conf. +Luego de modificar este archivo, necesitará reiniciar el proceso servidor para que los cambios sean efectivos. +

+

+Si usted verifica su configuración pero aún sigue obteniendo este mensaje, sigue siendo poco probable que +haya encontrado un fatal comportamiento erróneo de PostgreSQL. Usted probablemente tiene algún problema de conectividad de red de bajo nivel +(p.e. configuración del cortafuegos). Por favor verifique esto exhaustivamente antes de reportar + una falla a la comunidad PostgreSQL. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/fki.html (revision 1448) @@ -0,0 +1,38 @@ + + + + + +Sugerencias de Gurú + + + +

Índice que cubre una clave ajena (foreign key)

+

+Una clave ajena es usada para unir dos tablas en un modo lógico, y restringir los cambios que pueden ser aplicados a ellas. +

+

+Todo comienza con una tabla maestra, la cual será la tabla referenciada. Necesita tener una clave primaria (bien, realmente las +columnas referenciadas solo necesitan ser no nulas y cubiertas por un índice único, pero es realmente un buen consejo tener una +clave primaria). La tabla esclava depende de la tabla maestra, en el sentido que las columnas sobre las cuales +se crea la clave ajena deben coincidir con la tabla maestra para todas las claves insertadas o actualizadas. La tabla esclava es la tabla referenciante de la clave ajena. +

+

+La clave ajena no solo restringe a la tabla referenciante, sino también a la referenciada; el tipo de restricción puede ser +RESTRICT, CASCADE o SET NULL. Esto siginifica, que si una fila de la tabla maestra/referenciada es cambiada (actualizada +o eliminada), todas las tablas referenciantes son verificadas para ver si la operación es válida, y si hay alguna acción adicional a ejecutar; +vea la documentación de PostgreSQL acreca de claves ajenas (foreign keys) para mayores detalles. +

+

+Esto significa que a cada acceso de actualización a una fila específica de la tabla referenciada, una correspondiente lectura es ejecutada en cada una de las +tablas referenciantes, usando las columnas de la clave ajena como clave de acceso. Consecuentemente, todas las reglas de diseño que deberían ser tomadas +en cuenta para buenas prestaciones de lectura usualmente también se aplican a las columnas en una tabla referenciante. Para buena prestación, +un índice es aconsejable en la mayoría de los casos. PostgreSQL no obliga a ello de ninguna forma, así que depende del diseñador de la base de datos el proveer un índice. +

+

+Como un conveniencia, pgAdmin III provee una simple casilla de verificación cuando se crea una clave ajena, que verificará automáticamente +la presencia de un índice usable, y creará uno por usted si no se encuentra uno. Como con todos los índices, hay casos raros donde tal índice degrada un poco sus prestaciones totales, pero en general la falta de índices degrada más las prestaciones que tener demasiados. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,27 @@ + + + + + +Sugerencias de Gurú + + + + +

Codificación Unicode en un servidor Win32

+

+La base de datos es creada para usar codificación Unicode (UTF8) para almacenar datos y +es operada en un servidor PostgreSQL 8.0 coriendo en un servidor Win32. +

+

+La implementación Win32 de PostgreSQL 8.0 no es capaz de ordenar cadenas de caracteres de acuerdo a +secuencias de ordenamiento correctas, debido a que el sistema operativo no ofrece suficiente +soporte para ello. +

+

+Para esta instalación, se recomienda usar una codificación especifica de su localización, correr el cluster en +un sistema operativo diferente o actualizar su cluster de base de datos a PostgreSQL 8.1 que tiene +código adicional para resolver este problema de ordenamiento unicode. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/pk.html (revision 1448) @@ -0,0 +1,36 @@ + + + + + +Sugerencias de Gurú + + + + +

Claves primarias

+

+Al diseñar una tabla, debería siempre tener en mente cómo va a ser accedida dicha tabla +después. En la mayoría de los casos, necesitará un identificador para poder direccionar unívocamente una fila +específica; este identificador debería ser creado como su clave primaria. Una clave primaria no necesariamente +consiste en una sola columna; puede contener tantas columnas como sea necesario para identificar +unívocamente una fila. Si necesita varias columnas (regla "a dedo": más de 3), puede ser una buena +idea inventar una columna adicional con un tipo de datos conveniente, p.e. serial o bigserial, que contenga la clave primaria. +

+

+Sólo en casos raros no tiene sentido usar una clave primaria. Esto siginifica, la falta de clave primaria es un fuerte indicador +de una tabla no diseñada completamente; por eso es que una Sugerencia de Gurú aparecerá si usted crea una tabla +sin clave primaria +

+

+Si usted mira las tablas de sistema de PostgreSQL, encontrará que ninguna de ellas tiene clave primaria, así qué es esto? +Realmente, todas estas tablas tienen una o dos columnas (usualmente solo OID) que identifican unívocamente cada fila, obedeciendo la +segunda regla para una clave primaria, no permitiendo cero, y siendo cubierta por un índice para más rápido acceso. El uso de los OID tiene +razones históricas, y realmente no es la primera opción al diseñar tablas de usuarios. PostgreSQL aún usa esto para mantener la compatibilidad hacia atrás, +y mientras una nueva aproximación podría usar claves primarias explícitas esto no será cambiado más. +

+

+Como muestra el caso de las tablas de sistema, el objetivo de unicidad y rápido acceso puede ser logrado con otros medios que una clave primaria. De todos modos, por la claridad del modelo de datos, le recomendamos enfáticamente que use claves primaria para este propósito. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Sugerencias de Gurú + + +

+pgAdmin III ha encontrado múltiples problemas en el objeto corriente. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/es_ES/tips.txt (revision 1448) @@ -0,0 +1,46 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +La performance de PostgreSQL puede ser mejorada ejecutando VACUUM en sus bases de datos regularmente. +El cumpleaños oficial de PostgreSQL es el 8 de julio. El proyecto PostgreSQL nació en 1996. +El primer prototipo del proyecto original pgAdmin fue llamado pgManager y fue escrito para PostgreSQL 6.3.2. +Se puede solicitar soporte para pgAdmin a través de la lista de correo pgadmin-support@postgresql.org. +Las nuevas capacidades y desarrollos son discutidos por los Desarrolladores de pgAdmin a través de la lista de correo pgadmin-hackers@postgresql.org. +La mayoría de la librería pgSchema usada por pgAdmin II fue desarrollada en una laptop Windows 2000 en frente de un TV cerca de Oxford, Inglaterra! +Usted puede cambiar su contraseña seleccionando 'Cambiar la contraseña...' en el menu 'Archivo'. +El Panel de Definición muestra el código SQL generado por ingeniería inversa para el objeto seleccionada. +La respuesta para la pregunta de la Vida, el Universo y Todo es 42. +El núcleo de desarrolladores de pgAdmin está basado en Reino Unido, Francia, Alemania, Italia y Estados Unidos de America. +PostgreSQL 7.2 y superior soporta tablas sin columna OID para disminuir el uso de OID. +Usted puede monitorer la actividad del sistema por conexión usando la herramienta Estado. +Hay un buen número de archivos útiles, herramientas y proyectos incluidos con PostgreSQL en el directorio /contrib del árbol de fuentes. +Los lenguajes procedurales de PostgreSQL incluyen pl/pgSQL, pl/Python, pl/TCL, pl/Perl y pl/sh. +pgAdmin II fue descargado más de 10,000 veces *antes* que la primera versíon de calidad estuviera disponible! +La primera versión estable de pgAdmin II fue descargada más de 35,000 veces en los primeros 6 meses posteriores a su lanzamiento. +El proyecto Slony-I de www.slony.info puede ser utilizado para replacación Mestro -> Esclavo. +La primera version oficial estable de pgAdmin II fue liberada el 16 de enero de 2002. +El desarrollo del proyecto pgAdmin III comenzó el 29 de setiembre de 2002. +pgAdmin III es una versión completamente nueva de pgAdmin escrita en C++ usando el entorno wxWidgets para permitir su ejecución en sistemas Windows y *nix. +pgAdmin es liberado bajo la licencia Open Source 'Artistic Licence'. +PostgreSQL 7.3 soporta esquemas (schemas), que son espacios de nombres individuales dentro de bases de datos. +Los dominios (domains) pueden ser usados para crear tipos de datos predefinidos basados en tipos más genéricos.. +pgAdmin III 1.0.0 fue empaquetado para su liberación el 26 de setiembre de 2003. +El planificador de PostgreSQL ignorará su deseo de elegir un barrido por índice si los tipos de columnas vinculadas no coinciden. +Usted no debe nunca 'kill -9' al proceso postmaster!! +Los botones 'EXPLAIN ANALYZE' y 'Explain Query' son sus amigos para optimizar las consultas SQL. +PostgreSQL 8.0 agregó nuevas importantes prestaciones a nuestra DBMS incluyendo savepoints, tablespaces y la largamente esperada version para Windows. +pgAdmin III soporta conexiones encriptadas con SSL. +El nuevo port PostgreSQL para Win32 pasó todos los tests de regresión por primera vez el 24-10-2004. +El port de PostgreSQL para Windows fue descargado más de 45,000 veces en los cinco días posteriores al lanzamiento! +El error "Don't enable the OK button when setting the ACL for as-yet-uncreated objects" fue corregido a 39,000 pies sobre Finlandia mientras Andreas, Magnus y Dave volvían de una presentación de Slony-I y pgAdmin III en Japón! +Configurar PostgreSQL con demasiados shared buffers puede tener un efecto negativo en la performance debido a que reduce la memoria RAM disponible que el kernel de sistema operativo utiliza como cache del sstema de archivos. +Sitting on a plane for 12 hours is really mind numbingly boring which is why I'm writing new tips right now!! +El Grupo de Usuarios de PostgreSQL de Japón o JPUG tiene más de 5000 miembros y está creciendo todo el tiempo. +pgAdmin 1.4 está soportado en más plataformas que cualquier versión previa, incluyendo numerosas distribuciones Linux, Microsoft Windows (tm), FreeBSD, Solaris y Mac OS X. +pgAdmin 1.4 incluye una herramienta gráfica EXPLAIN para permitirle leer y entender más fácilmente los planes de consultas. +pgAgent puede ser usado para programar tareas batch y SQL, tales como recrear índices sensibles a fechas o eliminar registros antiguos. +Es una buena práctica definir lógica de la aplicación en la misma base de datos usando funciones y vistas. Esto asegura que diferentes front-ends de sus productos verán siempre las mismas vistas y actualizarán y modificarán datos de la misma forma. Mejor aún, usted tiene que escribirla sólo una vez para todos los front-ends! +Para ayudar a mantener sus bases de datos seguras, minimize la cantidad de accesos que permite a host remotos cuando crea su archivo de configuración pg_hba.conf, y siempre use conexiones encriptadas a menos que tenga buenas razones para no hacerlo. +Usted puede restringir el acceso a columnas individuales de una tabla para un usuario particular o grupo denegándole acceso directo a la tabla, y creando una vista conteniendo sólo las columnas que deberían ver. Si sus usuarios necesitan actualizar datos, puede crear reglas para aplicar las actualizaciones a la vista a la tabla en cambio. +PostgreSQL ha sido ejecutado en diversas plataformas tales como Microsoft X Box, Sony PlayStation II, y Sharp Zaurus PDAs! +EnterpriseDB donó una Apple Powerbook al proyecto pgAdmin para ayudar a mejorar el port para Mac OS X port de pgAdmin y de suproducto derivado, EDB Studio. Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-ascii.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-ascii.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-ascii.html (revision 1448) @@ -0,0 +1,35 @@ + + + + + +Conseil d'expert + + + + +

Codage de la base de données

+

+La base de données a été créé pour stocker des données dans le codage +SQL_ASCII. Ce codage est seulement défini pour les caractères sur sept bits ; +la signification des caractères dont le huitième bit est positionné (caractères +non ASCII allant de 127 à 255) n'est pas définie. En conséquence, il n'est pas +possible pour le serveur de convertir les données vers d'autres codages. +

+

+Si vous stockez des données non ASCII dans la base, vous êtes fortement encouragé +à utiliser un bon codage représentant la locale de votre ensemble de caractères +pour retrouver le bénéfice des conversions automatiques vers les différents +codages client si nécessaire. Si vous stockez des données non ASCII dans une +base de données SQL_ASCII, vous pouvez rencontrer des problèmes avec des +caractères étranges écrit ou lu depuis la base de données, problèmes causés par +des soucis de conversion de code. Ceci pourrait vous amener beaucoup de problèmes +en accédant à la base de données avec des programmes clients et des pilotes +différents. +

+

+Pour la grande majorité des installations, le codage Unicode (UTF8) apportera la +plus grande flexibilité. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-ident.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-ident.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-ident.html (revision 1448) @@ -0,0 +1,43 @@ + + + + + +Conseil d'expert + + + + +

Échec de l'authentification via ident

+

+Le serveur n'a pas autorisé l'utilisateur courant : le serveur rapporte +

+

+ +

+

+Si ce message apparaît, l'entrée trouvée dans pg_hba.conf pour votre combinaison +client, utilisateur, base de données est configurée pour une authentification via +"ident". Certaines distributions, comme Debian, ont ceci par défaut. +Pour passer avec succès une authentification basée sur ident, vous avez besoin +d'une configuration supplémentaire ; voir l'aide de PostgreSQL pour cela. +Pour un débutant, il serait approprié d'utiliser une méthode d'authentification +différente ; les mots de passe cryptés avec MD5 est un bon choix pouvant être +configuré avec ceci : +

+

+host all all 192.168.0.0/24 md5 +

+

+Cet exemple autorise les accès à toutes les bases de données de tous les +utilisateurs sur le réseau privé 192.168.0.0/24 à condition que l'identification +se fasse via des mots de passe cryptés en MD5. +

+

+Vous pouvez utiliser l'éditeur du fichier pg_hba.conf intégré à pgAdmin III pour +modifier le fichier de configuration pg_hba.conf. Après l'avoir modifié, vous +aurez besoin de demander le rechargement de la configuration du serveur en +utilisant pg_ctl ou en arrêtant puis en redémarrant le processus serveur. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/vacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/vacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/vacuum.html (revision 1448) @@ -0,0 +1,40 @@ + + + + + +Conseil d'expert + + + + +

Exécuter VACUUM est recommandé

+

+Le nombre de lignes estimés sur la table "" dévie +significativement du nombre de lignes réelles. Vous devez lancer VACUUM ANALYZE +sur cette table. +

+Au lieu d'exécuter une commande VACUUM ANALYZE manuellement sur cette table +(vous pouvez utiliser menu de maintenance de pgAdmin III pour cela), exécuter +VACUUM ANALYZE sur une base régulière, voire automatisée, doit être réfléchi. +Ceci se réalise en utilisant un outil de planification. PostgreSQL fournit aussi +le démon pg_autovacuum, qui conservera la trace des modifications réalisée sur +la base de données et lancera les commandes VACUUM automatiquement si nécessaire. +Dans la plupart des cas, pg_autovacuum sera le meilleur choix. +



+À quoi VACUUM est-il bon ? +

+Le planificateur de requêtes de PostgreSQL prend des décisions sur des +suppositions, réalisées à partir du nombre de lignes estimées. Si le nombre de +lignes réel est trop différent du nombre de lignes supposé, le planificateur +pourrait prendre une mauvaise décision, résultant en un plan de requête qui n'est +pas optimal. Ceci peut avoir comme conséquences des performances pauvres. +

+Le stockage de PostgreSQL nécessite l'utilisation de VACUUM pour que les +identifiants de transaction soient corrigés dans les tables. De plus, les lignes +obsolètes ne sont pas nettoyées tant que la commande VACUUM n'a pas été exécutée +sur cette table. Des informations en profondeur sont disponibles dans la +documentation en ligne, appuyez simplement sur le bouton d'aide. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/instrumentation.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/instrumentation.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/instrumentation.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Conseil d'expert + + + + +

Outils serveur

+

+Il manque des outils au serveur. +

+

+pgAdmin III utilise certaines fonctions de support qui ne sont pas disponibles +par défaut dans toutes les versions de PostgreSQL. Elles activent certaines +tâches qui rendent la vie plsu facile lors du traitement des journaux de trace +et des fichiers de configuration. +

+

+Lorsque vous avez installé PostgreSQL 8.0 ou supérieur en utilisant l'installeur +Windows, vous avez besoin d'activer l'option admin. +

+

+Lors de la compilation à partir des sources, les fichiers nécessaires sont +disponibles dans le sous-répertoire xtra du répertoire des sources de pgAdmin. +Pour PostgreSQL 8.0, copiez le répertoire admin sous le répertoire des sources +des contributions PostgreSQL et lancez make puis make +install à partir de là. Pour PostgreSQL 8.1, utilisez le répertoire +admin81 pour cela. Après l'installation du module, vous aurez besoin de créer +les fonctions outils dans votre base de données de maintenance en utilisant le +script admin.sql (admin81.sql pour PostgreSQL 8.1), situé dans le répertoire share +de PostgreSQL (par exemple /usr/local/pgsql/share). +

+

+Les outils serveur étendus ne sont pas supportés pour les versions 7.3 et 7.4 de +PostgreSQL. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/view-without-pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/view-without-pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/view-without-pk.html (revision 1448) @@ -0,0 +1,26 @@ + + + + + +Conseil d'expert + + + + +

Modifier les données d'une table sans clé primaire

+

+Comme la table ne dispose pas de clé primaire ou d'OID, vous pouvez seulement +visualiser les données. Insérer de nouvelles lignes et modifier les lignes +existantes n'est pas possible pour l'outil Modification des données +sans clé primaire. +

+

+Pour modifier les données, pgAdmin III a besoin d'une clé primaire sur la table, +ce qui est une bonne pratique lors de la conception d'une base de données. +Sinon, la table peut être créée avec l'option WITH OIDS. Notez que les OID n'ont +aucune garanties d'être uniques sur une très longue période de temps, donc +utiliser des OID comme clé primaire est seulement un choix secondaire. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-hba.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-hba.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-hba.html (revision 1448) @@ -0,0 +1,46 @@ + + + + + +Conseil d'expert + + + + +

Accès refusé à la base de données

+

+Le serveur n'a pas autorisé l'accès à la base de données : le serveur +rapporte +

+

+ +

+

+Pour accéder à la base de données sur un serveur PostgreSQL, vous devez tout +d'abord autoriser l'accès au serveur pour votre client (authentification basée +sur l'hôte). PostgreSQL vérifiera le fichier pg_hba.conf si un modèle +correspondant à votre adresse, nom d'utilisateur, base de données est présent et +activé avant même que les listes de contrôle d'accès SQL ne soient évaluées. +

+

+La configuration initiale de pg_hba.conf est assez restrictive pour éviter des +failles de sécurité involontaires causées par une configuration non acceptée. +Vous souhaiterez probablement quelque chose comme +

+

+host all all 192.168.0.0/24 md5 +

+

+Cet exemple autorise les accès à toutes les bases de données de tous les +utilisateurs sur le réseau privé 192.168.0.0/24 à condition que l'identification +se fasse via des mots de passe cryptés en MD5. +

+

+Vous pouvez utiliser l'éditeur du fichier pg_hba.conf intégré à pgAdmin III pour +modifier le fichier de configuration pg_hba.conf. Après l'avoir modifié, vous +aurez besoin de demander le rechargement de la configuration du serveur en +utilisant pg_ctl ou en arrêtant puis en redémarrant le processus serveur. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/autovacuum.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/autovacuum.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/autovacuum.html (revision 1448) @@ -0,0 +1,32 @@ + + + + + +Conseil d'expert + + + + +

Utiliser pg_autovacuum est recommandé

+

+À partir de PostgreSQL 8.1, le processus pg_autovacuum qui était anciennement +implémenté en tant que processus externe est maintenant complètement intégré +dans le moteur. Il lancera VACUUM automatiquement si un nombre configurable de +données a été modifiée. +

+

+Exécuter VACUUM est nécessaire sur un serveur PostgreSQL pour conserver la +cohérence des données ainsi que les performances du serveur. Pour commencer, il +est recommandé d'activer le démon pg_autovacuum en initialisant les paramètres +'autovacuum', 'stats_start_collector' et 'stats_row_level' du fichier +postgresql.conf à la valeur 'on'. Avec une pénalité habituellement négligeable +sur les performances, vous gagnerez avec l'exécution automatique des VACUUM. +

+

+Pour ajuster les performances de pg_autovacuum à vos besoins personnels, vous +pouvez avoir besoin de configurer plus finement les paramètres globaux ou les +paramètres inhérents à chaque table. Voir la documentation. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-listen.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-listen.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/conn-listen.html (revision 1448) @@ -0,0 +1,53 @@ + + + + + +Conseil d'expert + + + + +

Le serveur n'écoute pas

+

+Le serveur n'accepte pas les connexions : la bibliothèque de connexion +rapporte +

+

+ +

+

+Si vous rencontrez ce message, merci de vérifier que le serveur que vous essayez +de contacter est réellement en cours d'exécution sur le port donné. Testez si +vous avez une connexion réseau à partir de votre client vers le serveur hôte en +utilisant ping ou des outils équivalents. Votre réseau / VPN / tunnel SSH/ parefeu +est-il configuré correctement ? +

+

+Pour des raisons de sécurité, PostgreSQL n'écoute pas sur toutes les +adresses IP disponibles sur le serveur par défaut. Pour accéder au serveur sur +le réseau, vous devez activer l'coute sur l'adresse en premier lieu. +

+

+Pour les serveurs PostgreSQL, à partir de la version 8.0, ceci est contrôlé en +utilisant le paramètre "listen_addresses" dans le fichier +postgresql.conf. Vous pouvez y saisir une liste d'adresses IP que l serveur devra écouter ou simplement '*' pour indiquer toutes les adresses IP disponibles. +Pour les versions précédentes (7.3 ou 7.4), vous aurez besoin de configurer le +paramètre "tcpip_socket" à 'true'. +

+

+Vous pouvez utiliser l'éditeur de postgresql.conf intégré à pgAdmin III pour +modifier le fichier de configuration postgresql.conf. Après avoir modifié ce +fichier, vous devez redémarrer le processus serveur pour que les modifications +soient prises en compte. +

+

+Si vous avez bien vérifié votre configuration mais que vous obtenez toujours ce +message d'erreur, il est toujours improbable que vous ayez rencontré un +mauvais comportement de PostgreSQL. Vous avez certainement des problèmes de +connexion réseau (par exemple suivant la configuration du parefeu). Merci de +vérifier ceci en profondeur avant de rapporter un bogue à la communauté +PostgreSQL. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/fki.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/fki.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/fki.html (revision 1448) @@ -0,0 +1,54 @@ + + + + + +Conseil d'expert + + + +

Foreign key covering indexes

+

+Une clé étrangère est utilisée pour coupler deux tables d'une façon logique et +restreint les modifications qui peuvent les affecter. +

+

+Tout commence avec une table maître qui sera la table référencée. Elle doit avoir +une clé primaire (en fait, les colonnes référencées doivent seulement être non +NULL et doivent avoir un index unique mais un conseil vraiment bon est d'avoir une +clé primaire). La table esclave dépend de la table maître, dans le sens où les +colonnes sur lesquelles est ajoutée la clé étrangère créée doivent correspondre +à la table maître pour toute clé insérée ou mise à jour. La table esclave est la +table référante de la clé étrangère. +

+

+La clé étrangère ne restreint pas seulement la table référante mais aussi la +table de référence ; cette restriction peut être RESTRICT, CASCADE ou SET +NULL. Cela signifie que, si une ligne est modifiée dans la table +maître/référencée (mise à jour ou supprimée), toutes les tables référantes sont +vérifiées si l'opération est valide et s'il reste des actions supplémentaires à +réaliser ; voir la documentation de PostgreSQL sur les clés étrangères pour +plus de détails. +

+

+Ceci signifie que suite à un accès en modification sur une ligne spécifique dans +la table référencée, une lecture correspondante est réalisée sur toutes les +tables référantes en utilisant les colonnes de la clé étrangère comme clé d'accès. +En conséquence, toutes les règles de conception qui auraient dû être pris +en considération pour une lecture avec de bonnes performances devraient aussi +s'appliquer aux colonnes dans une table référante. Pour de bonnes performances, +un index est préférable dans la plupart des cas. PostgreSQL ne contraint pas +ceci de cette façon mais c'est au concepteur de la base de données de fournir un +index. +

+

+Pour plus de confort, pgAdmin III fournit une simple case à cocher lors de la +création d'une clé étrangère, qui vérifiera automatiquement la présence d'un +index utilisable et en créera un pour vous s'il n'existe pas. Comme avec tous les +index, il existe quelques rares cas où l'index fait décroître les performances +mais, en général, avoir un index de moins occasionne plus de dégradations au +niveau des performances que d'avoir un index de trop. +

+ + + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-unicode.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-unicode.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/encoding-unicode.html (revision 1448) @@ -0,0 +1,29 @@ + + + + + +Conseil d'expert + + + + +

Codage Unicode su un serveur Win32

+

+La base de données est créée pour utiliser le codage Unicode (UTF8) lors du +stockage des données sur un serveur PostgreSQL 8.0 fonctionnant sur une machine +Win32. +

+

+L'implémentation Win32 de PostgreSQL 8.0 n'est pas capable de trier les chaînes de +caractères suivant des séquences logiques appropriés car le système d'exploitation +n'offre pas de support suffisant pour cela. +

+

+Pour cette installation, il est recommandé d'utiliser un codage spécifique de la +locale, d'exécuter le cluster sur un système d'exploitation différent ou de mettre +à jour votre cluster de bases de données avec PostgreSQL 8.1 qui dispose d'un code +supplémentaire pour corriger ce problème. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/pk.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/pk.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/pk.html (revision 1448) @@ -0,0 +1,48 @@ + + + + + +Conseil d'expert + + + + +

Clés primaires

+

+Lors de la conception d'une table, vous devez toujours garder à l'esprit la façon +dont la table sera utilisée plus tard. Dans la plupart des cas, vous aurez besoin +d'un identifieur pour adresser de façon unique une ligne spécifique ; cet +identifieur devra être créé en tant que clé primaire. Une clé primaire ne consiste +pas nécessairement en une seule colonne ; elle peut contenir autant de +colonnes que nécessaire pour identifier une ligne de façon unique. Si vous avez +besoin de plusieurs colonnes (règle de base : plus de trois), une bonne +idée serait d'inventer une colonne supplémentaire avec un type de données +intéressant, c'est-à-dire serial ou bigserial, contenant la clé primaire. +

+

+Dans de rares cas, utiliser une clé primaire n'a pas de sens. Cela signifie +qu'une clé primaire manquante est un bon indicateur d'une table conçue +partiellement ; c'est pourquoi un conseil d'expert apparaîtra si vous créez +une base sans clé primaire. +

+

+Si vous regardez les tables système de PostgreSQL, vous n'en trouverez aucune +avec une clé primaire. Pourquoi ? +En fait, chacune de ces tables ont une ou deux colonnes (habituellement seulement +l'OID) qui identifient de façon unique chaque ligne, obéissant à la seconde +règle pour une clé primaire, n'autorisant pas zéro et étant couvert par un index +pour un accès plus rapide. L'utilisation des OID a une raison historique et n'est +pas vraiment un bon choix pour la conception de tables utilisateur. PostgreSQL +utilise toujours ceci pour des raisons de compatibilité ascendante et, bien +qu'une nouvelle approche utiliserait probablement des clés primaires explicites, +cela ne sera pas modifié. +

+

+Comme le montre le cas des tables système, le but d'unicité et d'accès rapide peut +être obtenu avec d'autres approches qu'une clé primaire. Malgré tout, pour la +clareté du modèle de données, vous êtes fortement encouragé à utiliser des clés +primaires dans ce but. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/multiple.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/multiple.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/hints/multiple.html (revision 1448) @@ -0,0 +1,13 @@ + + + + + +Conseil d'expert + + +

+pgAdmin III a découvert de nombreux problèmes sur l'objet en cours. +

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/bugreport.html =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/bugreport.html (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/bugreport.html (revision 1448) @@ -0,0 +1,41 @@ + + + + + +Rapport de bogue + + + + +

rapport de bogue

+ +

Si vous pensez avoir rencontré un bogue dans pgAdmin3, merci de vérifier la +liste suivante :

+
    +
  • Ce comportement est-il attendu ? jetez un œil aux + FAQ. +
  • Ce bogue est-il déjà rapporté ? + Vérifiez dans la liste + de discussion support. +
  • Utilisez-vous la dernière version du siet web beta ? Dans le cas + contraire, essayez la dernière version. +
+

Ahh, donc vous en avez trouvé un nouveau ? +

+

Postez votre rapport sur la liste de discussion support, +en incluant les informations suivantes :

+
    +
  • La plateforme utilisé +
  • La langue +
  • La distribution utilisée (archive tar des sources ou binaire) +
+

Après qu'un bogue soit indiqué corrigé sur la liste de discussion, +cela pourra prendre un jour ou deux avant qu'une nouvelle archive tar apparaisse, +soyez patient.

+

Merci de donner à pgAdmin3 une chance !

+

L'équipe de développement de pgAdmin

+ + Index: /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/tips.txt =================================================================== --- /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/tips.txt (revision 1448) +++ /pbibuild/modules/pgadmin/overlay-dir/share/pgadmin3/docs/fr_FR/tips.txt (revision 1448) @@ -0,0 +1,45 @@ +# To add a new tip, just add a new line to this file. +# Blank lines are ignored, lines starting with # are comments. + +Les performances de PostgreSQL peuvent être améliorées en exécutant VACUUM sur vos bases de données de façon réguliÚre. +La date anniversaire officielle de PostgreSQL est le 8 juillet. Le projet PostgreSQL est né en 1996. +Le premier prototype du projet pgAdmin original était nommé pgManager et a été écrit pour PostgreSQL 6.3.2. +Un support sur pgAdmin peut être demandé via la liste de discussions pgadmin-support@postgresql.org. +Les nouvelles fonctionnalités et les nouveaux développements sont discutés par les développeurs de pgAdmin sur la liste de discussion pgadmin-hackers@postgresql.org. +La majorité de la bibliothÚque pgSchema utilisée par pgAdmin II a été développée sur un portable sous Windows 2000 en face d'une télévision prÚs d'Oxford, Angleterre ! +Vous pouvez modifier votre mot de passe en sélectionnant 'Modifier le mot de passe' à partir du menu 'Fichier'. +Le panneau Définition affiche le SQL permettant la création de l'objet sélectionné. +La signification de la Vie, de l'Univers et de Tout est 42. +Les développeurs de pgAdmin sont basés en Angleterre, en France et aux États-Unis. +PostgreSQL 7.2 supporte les tables sans colonne OID pour autoriser l'élimination de l'utilisation des OID. +À partir de PostgreSQL 7.2, vous pouvez surveiller l'activité systÚme par connexion en utilisant 'SELECT * FROM pg_stat_activity'. +Il existe un certain nombre de fichiers, outils et projets utiles inclus avec PostgreSQL dans le sous-répertoire /contrib du répertoire des sources. +Les langages de procédure de PostgreSQL incluent pl/pgSQL, pl/Python, pl/TCL, pl/Perl et pl/sh. +pgAdmin II a été téléchargé plus de 10 000 fois *avant* la disponibilité de la premiÚre version de qualité ! +La premiÚre version stable de pgAdmin II a été téléchargée plus de 35 000 fois dans les six premiers mois suivant sa sortie. +La premiÚre version stable officielle de pgAdmin II a été sortie le 16 janvier 2002. +Le développement du projet pgAdmin III a commencé le 29 septembre 2002. +pgAdmin III est une version complÚtement nouvelle de pgAdmin écrite en C++ en utilisant l'environnement wxWindows pour lui permettre de fonctionner sur Windows et sur les systÚmes Unix. +pgAdmin est sortie sous la licence Open Source 'Artistic Licence'. +PostgreSQL 7.3 supporte les schémas qui sont des espaces de noms individuels dans les bases de données. +Les domaines peuvent être utilisés pour créer des types de données prédéfinies basées sur des types de base. +pgAdmin III 1.0.0 est sorti le 26 septembre 2003. +Le planificateur de PostgreSQL ignorera vos souhaits d'un parcours d'index si les types de données des colonnes jointes ne correspondent pas. +Vous ne devriez pas exécuter 'kill -9' sur le postmaster !! +'EXPLAIN ANALYZE' et le bouton 'Expliquer la requête' sont vos amis pour optimiser les requêtes SQL. +PostgreSQL 8.0 a vu l'arrivée de nouvelles fonctionnalités majeures comme les points de sauvegarde, les espaces logiques et le trÚs attendu port Windows. +pgAdmin III supporte les connexions chiffrées avec SSL. +Le nouveau port Win32 de PostgreSQL a réussi tous les tests de régression la premiÚre fois le 24 octobre 2004. +Le port Windows de PostgreSQL a été téléchargé 45 000 fois dans les cinq jours suivant sa sortie ! +Le bogue "N'active pas le bouton OK lors de l'initialisation des ACL pour les objets encore inexistants" a été corrigé à 39 000 pieds au-dessus de la Finlande quand Andreas, Magnus et Dave revenaient d'une présentation de Slony-I et pgAdmin III au Japon ! +Configurer PostgreSQL avec trop de tampons partagés peut avoir un effet négatif sur les performances car cela réduit la RAM disponible pour le cache du systÚme de fichiers créé par le systÚme d'exploitation. +Être assis dans un avion pendant plus de 12 heures est ennuyant, ce qui explique pourquoi j'écris de nouvelles astuces maintenant !! +Le groupe d'utilisateurs de PostgreSQL au Japon a plus de 5 000 membres, et il continue à grandir. +pgAdmin 1.4 est supporté sur plus de plateformes que la version précédente. Cela inclut de nombreuses distributions Linux, Microsoft Windows (tm), FreeBSD, Solaris et Mac OS X. +pgAdmin 1.4 inclut un outil graphique pour EXPLAIN, ce qui vous permet de lire et de comprendre plus facilement les plans de requête. +pgAgent peut être utilisé pour planifier des travaux réguliers, comme la re-création d'index partiels ou la purge d'anciens enregistrements. +Intégrer la logique de l'application dans la base de données grâce aux fonctions et vues est une bonne pratique. Cela vous assure que différentes interfaces produiront toujours les mêmes vues des données, et modifieront vos données de la même façon. Encore mieux, vous n'aurez qu'à les écrire une fois pour toutes les interfaces ! +Pour conserver vos bases en toute sécurité, minimisez le nombre d'accÚs que vous permettez aux hÃŽtes distants lors de la création de votre fichier pg_hba.conf. Utilisez toujours des connexions cryptées sauf si vous avez une bonne raison de ne pas le faire. +Vous pouvez restreindre l'accÚs aux colonnes individuelles d'une table pour un utilisateur ou un groupe particulier en lui refusant l'accÚs à cette derniÚre, et en créant une vue accessible à cet utilisateur et contenant seulement les colonnes qu'il peut voir. Si vos utilisateurs ont besoin de modifier les données, vous pouvez créer des rÚgles pour appliquer des mises à jour de la vue sur la table. +PostgreSQL fonctionne sur diverses plateformes, dont Microsoft X Box, Sony PlayStation II et les PDA Zaurus de Sharp ! +EnterpriseDB a donné un Apple Powerbook au projet pgAdmin pour aider à l'amélioration du port Mac OS X de pgAdmin et de leur version dérivée, EDB Studio. Index: /pbibuild/modules/pgadmin/pbi.conf =================================================================== --- /pbibuild/modules/pgadmin/pbi.conf (revision 1440) +++ /pbibuild/modules/pgadmin/pbi.conf (revision 1448) @@ -33,5 +33,5 @@ # Build Key - Change this to anything else to trigger a rebuild # - The rebuild will take place even if port is still the same ver -BUILDKEY="01" +BUILDKEY="02" export PBIPORT MAKEOPTS PROGNAME PROGWEB PROGAUTHOR OTHERPORT PROGICON PROGLIBS PBIUPDATE BUILDKEY