Re: WIN1252 patch broke my database - Mailing list pgsql-hackers

From Tom Lane
Subject Re: WIN1252 patch broke my database
Date
Msg-id 8352.1111162873@sss.pgh.pa.us
Whole thread Raw
In response to Re: WIN1252 patch broke my database  (Peter Eisentraut <peter_e@gmx.net>)
List pgsql-hackers
Peter Eisentraut <peter_e@gmx.net> writes:
> Am Donnerstag, 17. M�rz 2005 19:23 schrieb Tom Lane:
>> It doesn't eliminate the need for initdb, because pg_conversion contains
>> instances of the client-only encoding numbers.  I think that clients
>> know the client-only encoding numbers too, so I'm not sure we aren't
>> stuck with a compatibility issue.

> I think the problem case was old pg_dump versions saving the encoding number 
> rather than name.  I don't recall any problems with renumbering the client 
> encodings.  I believe that we in fact did that in 8.0.

As long as client code only uses the names, I suppose we are OK.  I'm a
bit worried about that assumption though, since it's not like the
numbers aren't exposed to view in pg_database and pg_conversion ...
        regards, tom lane


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: WIN1252 patch broke my database
Next
From: Bruce Momjian
Date:
Subject: Re: "they only drink coffee at dec"