| From: | Joe Abbate <jma(at)freedomcircle(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Selecting user-defined CASTs |
| Date: | 2011-08-09 13:49:12 |
| Message-ID: | 4E413AD8.9000602@freedomcircle.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 08/09/2011 01:27 AM, Tom Lane wrote:
> Another approach is to check pg_depend. A cast installed by initdb will
> match a "pin" entry in pg_depend (refclassid = pg_cast, refobjid =
> cast's OID, deptype = 'p'). You're still out of luck for distinguishing
> extension members in existing releases, but in 9.1 and up it'll be
> possible to identify casts belonging to extensions from pg_depend
> entries.
Intriguing alternative.
The query is for my dbtoyaml utility which is sort of equivalent to
pg_dump -s --format=y (yaml). So for now, I'll stick to emulating what
dumpCast in pg_dump.c does.
Joe
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2011-08-09 13:49:30 | Re: Problem with sources. |
| Previous Message | Kevin Grittner | 2011-08-09 13:41:26 | Re: WIP fix proposal for bug #6123 |