From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump doesn't dump binary compatible casts |
Date: | 2003-09-23 15:52:05 |
Message-ID: | 17710.1064332325@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Jan Wieck <JanWieck(at)Yahoo(dot)com> writes:
> I classify this problem as a bug. Objections?
The question is not whether it is a bug, the question is what is correct
behavior instead.
> IMHO a binary compatible cast should be dumped if one or both namespaces
> of the underlying data types is included in the dump.
That would just replace one bug with another (viz, failure to restore
if one of the datatypes wasn't included in the dump). Also, what of
user-defined casts between two system datatypes? pg_catalog is never
considered part of the dump AFAIR.
The first idea that came to mind is to dump the cast if both underlying
types are either system types or included in the dump. But I think that
would end up dumping built-in binary casts, which is no good either.
I hate to think of looking at the cast's OID vs. lastsysoid to decide
if it was a built-in cast, but maybe there's no other way.
Ideas anyone?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2003-09-23 16:01:14 | Re: [GENERAL] Can't Build 7.3.4 on OS X |
Previous Message | Jan Wieck | 2003-09-23 15:29:03 | pg_dump doesn't dump binary compatible casts |