Re: default client encoding in postgresql.conf

From: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: default client encoding in postgresql.conf
Date: 2008-06-13 02:58:14
Message-ID: 200806122258.14633.xzilla@users.sourceforge.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thursday 12 June 2008 21:11:57 Tom Lane wrote:
> Robert Treat <xzilla(at)users(dot)sourceforge(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2008-06-13 04:35:33 Re: default client encoding in postgresql.conf
Previous Message Bryce Nesbitt 2008-06-13 02:52:59 Re: TODO Item: Allow pg_hba.conf to specify host names along with IP addresses