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

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
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 06:30:54
Message-ID: 3f3e047b-f1e4-3857-8e20-dd69c604ff43@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fabien COELHO 2016-11-26 06:39:02 Re: confusing checkpoint_flush_after / bgwriter_flush_after
Previous Message Tom Lane 2016-11-26 05:48:37 Re: macaddr 64 bit (EUI-64) datatype support