pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedDoc updates - pg_options
6+ messages / 3 participants
[nested] [flat]
* Doc updates - pg_options
@ 2000-04-08 19:23 Oliver Elphick <olly@lfix.co.uk>
2000-04-08 19:39 ` Re: Doc updates - pg_options Bruce Momjian <pgman@candle.pha.pa.us>
2000-04-08 19:51 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
0 siblings, 2 replies; 6+ messages in thread
From: Oliver Elphick @ 2000-04-08 19:23 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
I found there wasn't much documentation on pg_options, so I have prepared a
self-documenting pg_options.sample which is attached.
Oliver Elphick Oliver.Elphick@lfix.co.uk
Isle of Wight http://www.lfix.co.uk/oliver
PGP key from public servers; key ID 32B8FAA1
========================================
"Do not be anxious about anything, but in everything,
by prayer and supplication, with thanksgiving, present
your requests to God. And the peace of God, which
transcends all understanding, will guard your hearts
and your minds in Christ Jesus." Philippians 4:6,7
Attachments:
pg_options (text/plain, 7.5K) download
# pg_options file
# Documented for Debian release 7.0-0.beta4-1
# Copyright (c) Oliver Elphick <olly@lfix.co.uk>
# Licence: May be used without any payment or restriction, except that
# the copyright and licence must be preserved.
# pg_options controls certain options and tracing features of the
# PostgreSQL backend. It is read by postmaster and postgres before
# command line arguments are examined, so command line arguments
# will override any settings here.
# This file should be located at $PGDATA/pg_options. In Debian, this is
# a symbolic link to /etc/postgresql/pg_options.
# The capitalised words refer to the internal #defines in the source code
# which use these options. Options can be turned on and off while the
# postmaster is running by editing this file and sending a SIGHUP to
# the postmaster.
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# File format #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# option = integer : set option to the specified value
# option + : set option to 1
# option - : set option to 0
#
# Comments begin with #, whitespace is ignored completely.
# Options are separated by newlines (or by commas -- but why make it
# needlessly difficult to read the file?)
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# Tracing options #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# all [TRACE_ALL]
# This governs what tracing occurs. If it is 0, tracing is
# controlled by the more specific options listed below. Set this to 1
# to trace everything, regardless of the settings below; set to -1 to
# turn off all tracing.
#
# Any of these tracing options can be turned on with the command line
# option `-T "option[,...]"'
all = 0
# verbose [TRACE_VERBOSE] -- command line option `-d n' with n >= 1
# Turns on verbose tracing of various events
verbose = 0
# query [TRACE_QUERY] -- command line option `-d n' with n >= 2
# Traces the query string before and after rewriting
query = 0
# plan [TRACE_PLAN] -- command line option `-d n' with n >= 4
# Traces plan trees in raw output format (see also pretty_plan)
plan = 0
# parse [TRACE_PARSE] -- command line option `-d n' with n >= 3
# Traces the parser output in raw form (see also pretty_parse)
parse = 0
# rewritten [TRACE_REWRITTEN]
# Traces the query after rewriting, in raw form (see also pretty_rewritten)
rewritten = 0
# pretty_plan [TRACE_PRETTY_PLAN]
# shows indented multiline versions of plan trees (see also plan)
pretty_plan = 0
# pretty_parse [TRACE_PRETTY_PARSE]
# Traces the parser output in a readable form (see also parse)
pretty_parse = 0
# pretty_rewritten [TRACE_PRETTY_REWRITTEN]
# -- command line option `-d n' with n >= 5
# Traces the query after rewriting, in a readable form (see also rewritten)
pretty_rewritten = 0
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# Locks #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# TRACE_SHORTLOCKS
# This value is currently unused but needed as an index placeholder.
# It must be left set to 0, or mayhem may result, including segmentation
# violations, perhaps.
shortlocks = 0
# TRACE_LOCKS
# Enable or disable tracing of ordinary locks
locks = 0
# TRACE_USERLOCKS
# Enable or disable tracing of user (advisory) locks
userlocks = 0
# TRACE_SPINLOCKS
# Enables or disables tracing of spinlocks, but only if LOCKDEBUG was
# defined when PostgreSQL was compiled. (In the Debian release,
# LOCKDEBUG is not defined, so this option is inoperative.)
spinlocks = 0
# TRACE_LOCKOIDMIN
# This option is is used to avoid tracing locks on system relations, which
# would produce a lot of output. You should specify a value greater than
# the maximum oid of system relations, which can be found with the
# following query:
#
# select max(int4in(int4out(oid))) from pg_class where relname ~ '^pg_';
#
# To get a useful lock trace you can set the following pg_options:
#
# verbose+, query+, locks+, userlocks+, lock_debug_oidmin=17500
lock_debug_oidmin = 0
# TRACE_LOCKRELATION
# This option can be used to trace unconditionally a single relation,
# for example pg_listener, if you suspect there are locking problems.
lock_debug_relid = 0
# TRACE_NOTIFY
# Turn on tracing of asynchronous notifications from the backend.
notify = 0
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# Memory Allocation #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# These do not appear to be used at 7.0beta4
# TRACE_MALLOC
malloc = 0
# TRACE_PALLOC
palloc = 0
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# Statistics #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# The statistics options are not controlled by either TRACE_ALL, or
# by USE_SYSLOG. These options cannot be used togther with the
# command line option `-s'.
# TRACE_PARSERSTATS
# Prints parser statistics to standard error -- command line `-tpa[rser]'
parserstats = 0
# TRACE_PLANNERSTATS
# Prints planner statistics to standard error -- command line `-tpl[anner]'
plannerstats = 0
# TRACE_EXECUTORSTATS
# Prints executor statistics to standard error -- command line `-te[xecutor]'
executorstats = 0
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# options controlling run-time behaviour #
#+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++#
# OPT_LOCKREADPRIORITY
# lock priority, see lock.c -- Does not appear to be used
lock_read_priority = 0
# OPT_DEADLOCKTIMEOUT
# deadlock timeout; set this to a non-zero integer, which is the number
# of seconds that the backend should wait before deciding that it is in
# a deadlock and timing out. The system default is 1 second.
deadlock_timeout = 0
# nofsync [OPT_NOFSYNC] -- command line option `-F'
# If this is non-zero, fsync will be turned off; this means that saving
# to disk will be left to the normal operating system sync. If this
# option is zero, every transaction will trigger a sync to disk; this
# gives increased safety at the expense of performance.
nofsync = 0
# OPT_SYSLOG
# This controls the destination of [many] messages and traces:
# 0 : write to stdout or stderr
# 1 : write to stdout or stderr, and also through syslogd
# 2 : log only through syslogd
# [Not all messages have been converted to use routines controlled by
# this parameter; unconverted ones will print to stdout or stderr
# unconditionally and never to syslogd.]
syslog = 0
# OPT_HOSTLOOKUP
# enable hostname lookup in ps_status. If this is set, a reverse
# lookup will be done on the connecting IP address (for TCP/IP
# connections) for inclusion in the ps_status display.
hostlookup = 0
# OPT_SHOWPORTNUMBER
# show port number in ps_status. If this is set, the TCP port number
# will be included in the ps_status display (for TCP/IP connections).
showportnumber = 0
* Re: Doc updates - pg_options
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
@ 2000-04-08 19:39 ` Bruce Momjian <pgman@candle.pha.pa.us>
1 sibling, 0 replies; 6+ messages in thread
From: Bruce Momjian @ 2000-04-08 19:39 UTC (permalink / raw)
To: Oliver Elphick <olly@lfix.co.uk>; +Cc: PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
> I found there wasn't much documentation on pg_options, so I have prepared a
> self-documenting pg_options.sample which is attached.
pg_options.sample added. I was confused as to how pg_options got
configured. With this file, I see it now.
pg_options.sample will not install by default.
--
Bruce Momjian | http://www.op.net/~candle
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, Pennsylvania 19026
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Doc updates - pg_options
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
@ 2000-04-08 19:51 ` Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:03 ` Re: Doc updates - pg_options Bruce Momjian <pgman@candle.pha.pa.us>
1 sibling, 1 reply; 6+ messages in thread
From: Lamar Owen @ 2000-04-08 19:51 UTC (permalink / raw)
To: Oliver Elphick <olly@lfix.co.uk>; +Cc: Bruce Momjian <pgman@candle.pha.pa.us>; PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
Oliver Elphick wrote:
>
> I found there wasn't much documentation on pg_options, so I have prepared a
> self-documenting pg_options.sample which is attached.
Thanks Oliver. Consider it added (with minor modifications) to the
RPM's, if it doesn't get put in the main tarball first.
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Doc updates - pg_options
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
2000-04-08 19:51 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
@ 2000-04-08 20:03 ` Bruce Momjian <pgman@candle.pha.pa.us>
2000-04-08 20:22 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
0 siblings, 1 reply; 6+ messages in thread
From: Bruce Momjian @ 2000-04-08 20:03 UTC (permalink / raw)
To: Lamar Owen <lamar.owen@wgcr.org>; +Cc: Oliver Elphick <olly@lfix.co.uk>; PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
> Oliver Elphick wrote:
> >
> > I found there wasn't much documentation on pg_options, so I have prepared a
> > self-documenting pg_options.sample which is attached.
>
> Thanks Oliver. Consider it added (with minor modifications) to the
> RPM's, if it doesn't get put in the main tarball first.
>
It is in the tarball already.
--
Bruce Momjian | http://www.op.net/~candle
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, Pennsylvania 19026
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Doc updates - pg_options
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
2000-04-08 19:51 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:03 ` Re: Doc updates - pg_options Bruce Momjian <pgman@candle.pha.pa.us>
@ 2000-04-08 20:22 ` Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:34 ` Re: Doc updates - pg_options Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 6+ messages in thread
From: Lamar Owen @ 2000-04-08 20:22 UTC (permalink / raw)
To: Bruce Momjian <pgman@candle.pha.pa.us>; +Cc: Oliver Elphick <olly@lfix.co.uk>; PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
Bruce Momjian wrote:
>
> > Oliver Elphick wrote:
> > >
> > > I found there wasn't much documentation on pg_options, so I have prepared a
> > > self-documenting pg_options.sample which is attached.
> >
> > Thanks Oliver. Consider it added (with minor modifications) to the
> > RPM's, if it doesn't get put in the main tarball first.
> >
>
> It is in the tarball already.
Yeah, I got your message just shortly after Oliver's.
However, I'd like to see this installed alongside the other *.sample
files in PGLIB (and which initdb puts in PGDATA) (which I probably will
go ahead and do for the RPM, again, if you don't beat me to the punch
:-)). This late in beta, you may not want to do that in the main line --
for the RPM's, however, it is a simple matter for me to add an install
to pop it into both PGLIB and PGDATA. This is a _useful_
self-documenting sample. Thanks, Oliver!
--
Lamar Owen
WGCR Internet Radio
1 Peter 4:11
^ permalink raw reply [nested|flat] 6+ messages in thread
* Re: Doc updates - pg_options
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
2000-04-08 19:51 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:03 ` Re: Doc updates - pg_options Bruce Momjian <pgman@candle.pha.pa.us>
2000-04-08 20:22 ` Re: Doc updates - pg_options Lamar Owen <lamar.owen@wgcr.org>
@ 2000-04-08 20:34 ` Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 6+ messages in thread
From: Bruce Momjian @ 2000-04-08 20:34 UTC (permalink / raw)
To: Lamar Owen <lamar.owen@wgcr.org>; +Cc: Oliver Elphick <olly@lfix.co.uk>; PostgreSQL-development <pgsql-hackers@postgresql.org>; PostgreSQL-documentation <docs@postgresql.org>
> Yeah, I got your message just shortly after Oliver's.
>
> However, I'd like to see this installed alongside the other *.sample
> files in PGLIB (and which initdb puts in PGDATA) (which I probably will
> go ahead and do for the RPM, again, if you don't beat me to the punch
> :-)). This late in beta, you may not want to do that in the main line --
> for the RPM's, however, it is a simple matter for me to add an install
> to pop it into both PGLIB and PGDATA. This is a _useful_
> self-documenting sample. Thanks, Oliver!
Yes, it will install by default into /lib.
--
Bruce Momjian | http://www.op.net/~candle
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, Pennsylvania 19026
^ permalink raw reply [nested|flat] 6+ messages in thread
end of thread, other threads:[~2000-04-08 20:34 UTC | newest]
Thread overview: 6+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2000-04-08 19:23 Doc updates - pg_options Oliver Elphick <olly@lfix.co.uk>
2000-04-08 19:39 ` Bruce Momjian <pgman@candle.pha.pa.us>
2000-04-08 19:51 ` Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:03 ` Bruce Momjian <pgman@candle.pha.pa.us>
2000-04-08 20:22 ` Lamar Owen <lamar.owen@wgcr.org>
2000-04-08 20:34 ` Bruce Momjian <pgman@candle.pha.pa.us>
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