Search Postgresql Archives

Re: pg_dumpall: pg_conversion table not saved

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Michael Enke <michael.enke@xxxxxxxxxxxxxxxxxx> 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 update get lost.

pg_dump does not (and shouldn't) dump system-defined objects.  It has
no way to know that you modified the definition of such an object.

> Why can not the "CREATE DEFAULT CONVERSION ..."
>       a) return with an error if there is another default conversion existing or

AFAICS it does.

			regards, tom lane


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux