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
Subject: Re-ordering .CONF params ... questions for this list
Date: Tue, 10 Jun 2003 11:01:46 -0700
Message-ID: <200306101101.46304.josh@agliodbs.com> (raw)

Folks,

We've been discussing this for a while on HACKERS.  However, I haven't been 
getting much feedback on the specific order proposed.

Attached is an outline of my proposed re-ordering of postgresql.conf.sample.   
Please send me comments.  I need to submit a patch by Thursday, so don't take 
too long.

This is an effort to make the order of run-time params in 
postgresql.conf.sample and in the docs more logical and less baffling to the 
new DBA.

Questions:
1) Should "enable_implicit_from" go in the "Version/Platform Compatibility" 
section where I have it now, or in "CLIENT CONNECTIONS-Statement Behavior", 
or somewhere else?

2) Where should "preload_libraries" go?   I'm very reluctant to start a 
"Misc." section.  Perhaps I should start a "LIBRARIES" section?

3) I have re-ordered each subsection somewhat.   The fixed ordering is based 
on:
        a) My guess at the frequency with which that option will be changed, 
with more common options toward the top of the subsection;
        b) Grouping for tightly related options and for options that cascade;
        c) where (a) and (b) are unclear, alpha order.
Does this order make sense looking at the file?

3) Should we use indenting in PostgreSQL.conf.sample?   I tend to think it 
would make the file easier to read, but I'm not sure what effect it would 
have, if any, on parsing the file and whether other people would find it easy 
to read.



-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco

Attachments:

re_order_conf (text/plain, 2.4K) 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 Usage max_files_per_process #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 #CLIENT CONNECTION DEFAULTS #Statement Behaviour autocommit search_path default_transaction_isolation default_transaction_read_only statement_timeout #Locale and Formatting client_encoding australian_timezones datestyle timezone lc_messages lc_monetary lc_time lc_numeric #Other Defaults dynamic_library_path password_encryption #LOGGING & DEBUGGING #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 #Syslog syslog syslog_facility syslog_ident #STATISTICS #Statistics monitoring show_parser_stats show_planner_stats show_executor_stats show_statement_stats #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 enable_implicit_from have_rendezvous regex_flavor sql_inheritance transform_null_equals

view thread (9+ messages)  latest in thread

Message-ID: <200306101101.46304.josh@agliodbs.com>
Permalink:  ../200306101101.46304.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200306101101.46304.josh@agliodbs.com

 · 

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
  Subject: Re: Re-ordering .CONF params ... questions for this list
  In-Reply-To: <200306101101.46304.josh@agliodbs.com>
  References: <200306101101.46304.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