Andrew Dunstan <[EMAIL PROTECTED]> writes:
> Robert Treat wrote:
>>> 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.
> I should have thought there was a good ar
Robert Treat wrote:
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.
I should have thought there was a good argument for preventing its being
set in postg
On Thursday 12 June 2008 21:11:57 Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> 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 def
Robert Treat <[EMAIL PROTECTED]> 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
> t
On Thursday 12 June 2008 17:38:26 Tom Lane wrote:
> Robert Treat <[EMAIL PROTECTED]> writes:
> > looking in my freshly installed 8.3.3, I see this in the postgresql.conf
> > #client_encoding = sql_ascii# actually, defaults to database
> >
Robert Treat <[EMAIL PROTECTED]> 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
> Now, certainly initdb can't know
looking in my freshly installed 8.3.3, I see this in the postgresql.conf
#client_encoding = sql_ascii# actually, defaults to database
# encoding
Now, certainly initdb can't know for sure what encoding a future database will
b
