Re: pg_dumpall: pg_conversion table not saved

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Michael Enke <michael(dot)enke(at)wincor-nixdorf(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: pg_dumpall: pg_conversion table not saved
Date: 2008-05-07 21:38:12
Message-ID: 18976.1210196292@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Michael Enke <michael(dot)enke(at)wincor-nixdorf(dot)com> 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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Bruce Momjian 2008-05-07 21:38:50 Re: [GENERAL] pgbench not setting scale size correctly?
Previous Message Simon Riggs 2008-05-07 21:28:44 Re: Backup/Restore of single table in multi TB database