Re: References to arbitrary database objects that are suitable for pg_dump - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: References to arbitrary database objects that are suitable for pg_dump
Date
Msg-id 3f3e047b-f1e4-3857-8e20-dd69c604ff43@BlueTreble.com
Whole thread Raw
In response to Re: References to arbitrary database objects that are suitable for pg_dump  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [HACKERS] References to arbitrary database objects that aresuitable for pg_dump  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
List pgsql-hackers
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 
extensions.
-- 
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: macaddr 64 bit (EUI-64) datatype support
Next
From: Fabien COELHO
Date:
Subject: Re: confusing checkpoint_flush_after / bgwriter_flush_after