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

2017-01-18 Thread Alvaro Herrera
Jim Nasby wrote: > Is there anything that will translate an object identity (as returned by > pg_event_trigger_ddl_commands) into class/object/subobject OIDs? If I had > that, I could use it to track objects by OID (like pg_depend does), as well > as storing the text representation. That way I can

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

2016-12-10 Thread Jim Nasby
On 11/26/16 12:30 AM, Jim Nasby wrote: On 11/25/16 6:00 PM, Tom Lane wrote: OIDs? Then use pg_describe_object() to turn that into text when dumping. How would I get pg_dump to do that? I could certainly make this work if there was some way to customize how pg_dump dumps things, but AFAIK the

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

2016-11-25 Thread Jim Nasby
On 11/25/16 6:00 PM, Tom Lane wrote: OIDs? Then use pg_describe_object() to turn that into text when dumping. How would I get pg_dump to do that? I could certainly make this work if there was some way to customize how pg_dump dumps things, but AFAIK there's no way to do that, even with exte

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

2016-11-25 Thread Tom Lane
Jim Nasby 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 th