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

From Peter Eisentraut
Subject Re: WIN1252 patch broke my database
Date
Msg-id 200503181707.14566.peter_e@gmx.net
Whole thread Raw
In response to Re: WIN1252 patch broke my database  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: WIN1252 patch broke my database  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
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.

-- 
Peter Eisentraut
http://developer.postgresql.org/~petere/



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Query crashes/hangs server
Next
From: Tom Lane
Date:
Subject: Re: WIN1252 patch broke my database