Re: Proposal to Re-Order Postgresql.Conf, part II

From: Josh Berkus <josh(at)agliodbs(dot)com>
To: Justin Clift <justin(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Rod Taylor <rbt(at)rbt(dot)ca>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Proposal to Re-Order Postgresql.Conf, part II
Date: 2003-06-09 16:28:45
Message-ID: 200306090928.45767.josh@agliodbs.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom, Justin,

> Um, not documenting it is probably not a good move for us, however putting
> it at the end in a section marked "Developer Focused" or something similar
> would probably have the right mix of messages. i.e. "hands off" + "not a
> performance tweak", etc.

So, proposal:

1) wal_debug and the various trace_locks options will not be included in
postgresql.conf.sample

2) they will, however, be included in the "Run Time Configuration" page, under
a secion entitled "Source Develoment Options"

Work for everybody?

--
Josh Berkus
Aglio Database Solutions
San Francisco

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Kurt Roeckx 2003-06-09 17:18:34 Re: freeaddrinfo2 changes.
Previous Message Tom Lane 2003-06-09 15:46:57 Re: Some quick notes about extending libpq for new protocol