pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: Richard Huxton <richardh@archonet.com>
To: pgsql-performance@postgresql.org
Subject: Re: Re-ordering .CONF params ... questions for this list
Date: Tue, 10 Jun 2003 13:57:24 -0700
Message-ID: <200306101357.24596.josh@agliodbs.com> (raw)
In-Reply-To: <200306102005.11578.richardh@archonet.com>
References: <200306101101.46304.josh@agliodbs.com>
	<200306102005.11578.richardh@archonet.com>

Richard,

> Logging & Debugging
> I'd like this near the top, but then I use syslogging. With a new install I 
go 
> in and check tcpip_socket etc, fix the logging and just see if everything is 
> working. Then I go in and do a little tuning.
> Actually, maybe the syslog sub-section should go above the others - say 
where 
> you'll log to, and then what you'll log. Of course, I'm biased since I use 
> syslog.

I have no objection to moving the syslog section.  Any other opinions?

> Client Connection Defaults/Other/password_encryption
> This should probably go in the security section. Actually, looking at it 
> "dynamic_librar_path" is in the wrong place too - cut & past error?

Not the way I read the docs; according to the docs:

password_encryption is whether or not the statement "ALTER USER joe_schmoe 
WITH PASSWORD 'xxxyyy'" is encrypted by default even if you don't use the 
"WITH ENCRYPTION" option.   And it is SET-able on each client connection, by 
regular users.  So it goes in "CLIENT CONNECTION SETTINGS".

"dynamic_library_path", while less obvious, is also SETable on each client 
connection.   I'd be happy to revise this if someone understands/uses this 
option and has a better idea where to put it.

> Not sure it would help that much - the comments need a URL to the relevant 
> page in the online docs though. A couple more lines of comments too:

Given that we're running out of time, I wasn't going to touch any of the 
comments in PostgreSQL.conf.sample.   Instead, I was going to leave the 
comments as-is, and post extensive comments on Techdocs before 7.4 beta.  
Then, in 7.5 or 8.0 we can re-comment .conf.

-- 
-Josh Berkus
 Aglio Database Solutions
 San Francisco




view thread (9+ messages)  latest in thread

Message-ID: <200306101357.24596.josh@agliodbs.com>
Permalink:  ../200306101357.24596.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200306101357.24596.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, richardh@archonet.com
  Subject: Re: Re-ordering .CONF params ... questions for this list
  In-Reply-To: <200306101357.24596.josh@agliodbs.com>
  References: <200306101101.46304.josh@agliodbs.com> <200306102005.11578.richardh@archonet.com> <200306101357.24596.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