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 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
--
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general
