Re: default client encoding in postgresql.conf - Mailing list pgsql-hackers

From Robert Treat
Subject Re: default client encoding in postgresql.conf
Date
Msg-id 200806122258.14633.xzilla@users.sourceforge.net
Whole thread Raw
In response to Re: default client encoding in postgresql.conf  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: default client encoding in postgresql.conf  (Andrew Dunstan <andrew@dunslane.net>)
List pgsql-hackers
On Thursday 12 June 2008 21:11:57 Tom Lane wrote:
> Robert Treat <xzilla@users.sourceforge.net> writes:
> >>> looking in my freshly installed 8.3.3, I see this in the
> >>> postgresql.conf #client_encoding = sql_ascii            # actually,
> >>> defaults to database # encoding
> >
> > But isn't putting a default that is likely to be wrong just encouraging
> > people to set it to something more permanent as an attempt to "correct"
> > this?
>
> Huh?  We *aren't* putting in a default.
>

Right, but when you look in the postgresql.conf, it looks like we are setting 
the default to sql_ascii (since all other default values follow this 
commented setting formula). 

> This conversation is beginning to suggest to me that client_encoding
> shouldn't be listed in postgresql.conf at all.
>

Yeah, that sure seems better than what we currently have. 

-- 
Robert Treat
Build A Brighter LAMP :: Linux Apache {middleware} PostgreSQL


pgsql-hackers by date:

Previous
From: James William Pye
Date:
Subject: Re: Overhauling GUCS
Next
From: Andrew Dunstan
Date:
Subject: Re: default client encoding in postgresql.conf