Skip site navigation (1) Skip section navigation (2)

Re: problem with casts dump/restore

From: "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: problem with casts dump/restore
Date: 2005-01-11 19:09:45
Message-ID: 6EE64EF3AB31D5448D0007DD34EEB3412A75A7@Herge.rcsinc.local (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
> "Merlin Moncure" <merlin(dot)moncure(at)rcsonline(dot)com> writes:
> > I just noticed that pg_dump does not seem to be exporting at least
> > of my user defined casts...In particular, this one:
> > CREATE CAST (xid AS oid)
> This is per design, more or less:
>     /*
>      * As per discussion we dump casts if one or more of the
>      * objects (the conversion function and the two data types) are
>      * builtin AND if all of the non-builtin objects namespaces are
>      * included in the dump. Builtin meaning, the namespace name does
>      * start with "pg_".
>      */
> (The discussion in question is from late Sept 2003.)
> The problem is basically that there's no way to detect that this isn't
> built-in cast.
> In 7.3 and later there is another way to attack that question, which
> to look to see if there's a "pin" dependency in pg_depend for the
> Kinda ugly but it might do.

Hmm...well, that makes perfect sense.  I suppose it's easy enough to
work around the problem by splitting the cast in two, and that's not
necessarily bad style, IMO.

The reason why I did that to begin with was to be able to do some
in-query processing on a xid.  Is it intentional that oid has a built in
cast to integer and xid does not?



pgsql-hackers by date

Next:From: Andrew DunstanDate: 2005-01-11 19:44:24
Subject: buildfarm switching servers
Previous:From: Tom LaneDate: 2005-01-11 18:53:37
Subject: Re: problem with casts dump/restore

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group