pg.ddx.io pgsql-performance@postgresql.org mailing list archive
help / color / mirror / Atom feed From: Josh Berkus <josh@agliodbs.com>
To: pgsql-performance@postgresql.org
Cc: pgsql-hackers@postgresql.org
Subject: Re: Re-ordering .CONF params ... questions for this list
Date: Tue, 10 Jun 2003 14:45:13 -0700
Message-ID: <200306101445.13513.josh@agliodbs.com> (raw )
In-Reply-To: <200306101429.43003.josh@agliodbs.com >
References: <200306101101.46304.josh@agliodbs.com >
<5408.1055280523@sss.pgh.pa.us >
<200306101429.43003.josh@agliodbs.com >
Folks,
Revised ordering of options, based on information and suggestions received
here on both mailing lists.
--
-Josh Berkus
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh@agliodbs.com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Attachments:
re_order_conf (text/plain, 2.6K) download
#CONNECTIONS AND AUTHENTICATION
#Connection Settings
tcpip_socket
max_connections
superuser_reserved_connections
port
unix_socket_directory
unix_socket_group
unix_socket_permissions
#Security & Authentication
authentication_timeout
ssl
krb_server_keyfile
virtual_host
db_user_namespace
#RESOURCE USAGE (except WAL)
#Memory
shared_buffers
sort_mem
vacuum_mem
#Free Space Map
max_fsm_pages
max_fsm_relations
#Disk Resource Usage
max_files_per_process
preload_libraries
#WRITE AHEAD LOG
fsync
wal_sync_method
wal_buffers
checkpoint_segments
checkpoint_timeout
checkpoint_warning
commit_delay
commit_siblings
#QUERY TUNING
#Planner Method Enabling
enable_hashagg
enable_hashjoin
enable_indexscan
enable_mergejoin
enable_nestloop
enable_seqscan
enable_sort
enable_tidscan
#Planner Cost Constants
effective_cache_size
random_page_cost
cpu_tuple_cost
cpu_index_tuple_cost
cpu_operator_cost
default_statistics_target
#Genetic Estimate Query Optimizer
geqo
geqo_threshold
geqo_selection_bias
geqo_pool_size
geqo_effort
geqo_generations
geqo_random_seed
#Other Query Modifiers
explain_pretty_print
from_collapse_limit
join_collapse_limit
max_expr_depth
#LOGGING & DEBUGGING
#Syslog
syslog
syslog_facility
syslog_ident
#Debugging/Logging Levels
server_min_messages
client_min_messages
log_min_error_statement
debug_print_parse
debug_print_rewritten
debug_print_plan
debug_pretty_print
debug_assertions
silent_mode
#Additional Info to Log
log_connections
log_duration
log_pid
log_statement
log_timestamp
hostname_lookup
show_source_port
#CLIENT CONNECTION DEFAULTS
#Statement Behaviour
XXXXXautocommitXXXXX REMOVED!
search_path
default_transaction_isolation
default_transaction_read_only
statement_timeout
#Locale and Formatting
datestyle
timezone
australian_timezones
extra_float_digits
lc_messages
lc_monetary
lc_time
lc_numeric
client_encoding
#Other Defaults
password_encryption
dynamic_library_path
#STATISTICS
#Statistics monitoring
show_parser_stats
show_planner_stats
show_executor_stats
show_statement_stats
default_statistics_target
#Query/Index Statistics Collector
stats_start_collector
stats_reset_on_server_start
stats_command_string
stats_row_level
stats_block_level
#LOCK MANAGEMENT
deadlock_timeout
max_locks_per_transaction
#VERSION/PLATFORM COMPATIBILITY OPTIONS
#Previous Postgres Versions
enable_implicit_from
regex_flavor
sql_inheritance
#Compatibility with Platforms & Clients
have_rendezvous
transform_null_equals
view thread (9+ messages) latest in thread
Message-ID: <200306101445.13513.josh@agliodbs.com>
Permalink: ../200306101445.13513.josh@agliodbs.com/
Also on: postgresql.org/message-id/200306101445.13513.josh@agliodbs.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: josh@agliodbs.com, pgsql-hackers@postgresql.org
Subject: Re: Re-ordering .CONF params ... questions for this list
In-Reply-To: <200306101445.13513.josh@agliodbs.com>
References: <200306101101.46304.josh@agliodbs.com> <5408.1055280523@sss.pgh.pa.us> <200306101429.43003.josh@agliodbs.com> <200306101445.13513.josh@agliodbs.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox