Re: [GENERAL] pg_dumpall: pg_conversion table not saved

2008-05-08 Thread Michael Enke
Tom Lane schrieb: > Michael Enke <[EMAIL PROTECTED]> writes: >> I updated pg_converion to set the condefault=false where I need it. > > Why are you needing to replace an existing default conversion? > Do we have a bug in it? No, not a bug. But I need CP852 encoding conversion. Maybe you can take

Re: [GENERAL] pg_dumpall: pg_conversion table not saved

2008-05-07 Thread Martijn van Oosterhout
On Wed, May 07, 2008 at 05:38:12PM -0400, Tom Lane wrote: > Michael Enke <[EMAIL PROTECTED]> writes: > > I updated pg_converion to set the condefault=false where I need it. > > Why are you needing to replace an existing default conversion? > Do we have a bug in it? He doesn't really. See his mess

Re: [GENERAL] pg_dumpall: pg_conversion table not saved

2008-05-07 Thread Tom Lane
Michael Enke <[EMAIL PROTECTED]> writes: > I updated pg_converion to set the condefault=false where I need it. Why are you needing to replace an existing default conversion? Do we have a bug in it? > pg_dumpall does NOT write that table out and therefore it is not possible to > restore, this upd

[GENERAL] pg_dumpall: pg_conversion table not saved

2008-05-07 Thread Michael Enke
Hi list, I updated pg_converion to set the condefault=false where I need it. pg_dumpall does NOT write that table out and therefore it is not possible to restore, this update get lost. Anybody know if this is an error or has an explanation why it has to work this way? Background: I have created