Re: References to arbitrary database objects that are suitable for pg_dump

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
Cc: Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: References to arbitrary database objects that are suitable for pg_dump
Date: 2016-11-26 00:00:40
Message-ID: 1193.1480118440@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> writes:
> The challenge I'm running into is finding a way to store a reference to
> an arbitrary object that will survive a rename as well as working with
> pg_dump.

Can't you do it like pg_depend does, that is store the class and object
OIDs? Then use pg_describe_object() to turn that into text when dumping.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Paul Ramsey 2016-11-26 00:14:57 Re: User-defined Operator Pushdown and Collations
Previous Message Tom Lane 2016-11-25 23:57:58 Re: Fixed pg_class refcache leak when the meta tuple in pg_class in invalid.