Re: postgresql.conf and postgres options - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: postgresql.conf and postgres options
Date
Msg-id 200101241841.NAA09696@candle.pha.pa.us
Whole thread Raw
In response to Re: postgresql.conf and postgres options  (Peter Eisentraut <peter_e@gmx.net>)
Responses Re: postgresql.conf and postgres options
List pgsql-hackers
I have added all possible config options to postgresql.conf.sample.

I have attached the new version of the file.  I think you will be amazed
at how GUC gives us such powerful control over PostgreSQL.

Thanks, Peter.

> Oliver Elphick writes:
> 
> > 2.  The following command line options to postgres don't have an equivalent in
> >     postgresql.conf.  Is that intentional?  (I suppose it is in several cases,
> >     and I have left out some where it is obviously intentional.)  I can't see
> >     why these items can't be put in the configuration file:
> 
> >     -C        Noversion = true   [not documented in postgres man page]
> 
> This option doesn't do anything.
> 
> >     -D        potential_Datadir = arg      [set PGDATA]
> 
> This option can't be in the config file because it is used to *find* the
> config file.
> 
> >     -E        EchoQuery = true   [echo queries to log]
> 
> Hmm, there's debug_print_query.  This will probably be consolidated in the
> future.
> 
> >     -e        EuroDates = true   [use European format for dates]
> 
> This should be a config file option, but Thomas Lockhart couldn't make up
> his mind what to call it.  ;-)
> 
> >     -N        UseNewLine = 0     [newline is not a query separator]
> 
> I don't think this is useful.
> 
> >     -o        [set stdout, stderr to file arg]
> 
> I think this is broken or not well maintained.  Will be cleaned up in some
> later release.
> 
> -- 
> Peter Eisentraut      peter_e@gmx.net       http://yi.org/peter-e/
> 
> 


--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
853-3000+  If your life is a hard drive,     |  830 Blythe Avenue +  Christ can be your backup.        |  Drexel Hill,
Pennsylvania19026 
#
# PostgreSQL configuration file
# -----------------------------
#
# This file consists of lines of the form
#
#   name = value
#
# (The `=' is optional.) White space is collapsed, comments are
# introduced by `#' anywhere on a line. The complete list of option
# names and allowed values can be found in the PostgreSQL
# documentation. Examples are:

#log_connections = on
#fsync = off
#max_connections = 64

# Any option can also be given as a command line switch to the
# postmaster, e.g., 'postmaster -c log_connections=on'. Some options
# can be set at run-time with the 'SET' SQL command.


#========================================================================


#
#    Connection Parameters
#
#tcpip_socket = false
#ssl = false

#max_connections = 32 # 1-1024

#port = 5432 
#hostname_lookup = false
#show_source_port = false

#unix_socket_directory = ""
#unix_socket_group = ""
#unix_socket_permissions = 0777

#virtual_host = ""

#krb_server_keyfile = ""


#
#    Performance
#
#sort_mem = 512
#shared_buffers = 2*max_connections # min 16
#fsync = true


#
#    Optimizer Parameters
#
#enable_seqscan = true
#enable_indexscan = true
#enable_tidscan = true
#enable_sort = true
#enable_nestloop = true
#enable_mergejoin = true
#enable_hashjoin = true

#ksqo = false
#geqo = true

#effective_cache_size = 1000  # default in 8k pages
#random_page_cost = 4
#cpu_tuple_cost = 0.01
#cpu_index_tuple_cost = 0.001
#cpu_operator_cost = 0.0025
#geqo_selection_bias = 2.0 # range 1.5-2.0


#
#    GEQO Optimizer Parameters
#
#geqo_threshold = 11
#geqo_pool_size = 0  #default based in tables, range 128-1024
#geqo_effort = 1
#geqo_generations = 0
#geqo_random_seed = -1 # auto-compute seed


#
#    Inheritance
#
#sql_inheritance = true


#
#    Deadlock
#
#deadlock_timeout = 1000


#
#    Expression Depth Limitation
#
#max_expr_depth = 10000 # min 10


#
#    Write-ahead log (WAL)
#
#wal_buffers = 8 # min 4
#wal_files = 0 # range 0-64
#wal_debug = 0 # range 0-16
#commit_delay = 5 # range 0-1000
#checkpoint_timeout = 300 # range 30-1800


#
#    Debug display
#
#silent_mode = false

#log_connections = false
#log_timestamp = false
#log_pid = false

#debug_level = 0 # range 0-16

#debug_print_query = false
#debug_print_parse = false
#debug_print_rewritten = false
#debug_print_plan = false
#debug_pretty_print = false

#ifdef USE_ASSERT_CHECKING
#debug_assertions = true
#endif


#
#    Syslog
#
#ifdef ENABLE_SYSLOG
#syslog = 0 # range 0-2
#syslog_facility = "LOCAL0"
#syslog_ident = "postgres"
#endif


#
#    Statistics
#
#show_parser_stats = false
#show_planner_stats = false
#show_executor_stats = false
#show_query_stats = false
#ifdef BTREE_BUILD_STATS
#show_btree_build_stats = false
#endif


#
#    Lock Tracing
#
#trace_notify = false
#ifdef LOCK_DEBUG
#trace_locks = false
#trace_userlocks = false
#trace_spinlocks = false
#debug_deadlocks = false
#trace_lock_oidmin = 16384
#trace_lock_table = 0
#endif

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [INTERFACES] ODBC gives pq_recvbuf: unexpected EOF on client connection
Next
From: Tom Lane
Date:
Subject: Re: LEFT JOIN in pg_dumpall is a bug