Re: pg_dump selectively ignores extension configuration tables

From: Joe Conway <mail(at)joeconway(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndQuadrant(dot)fr>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_dump selectively ignores extension configuration tables
Date: 2013-03-15 00:23:59
Message-ID: 51426A1F.9080600@joeconway.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 03/13/2013 04:16 PM, Dimitri Fontaine wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>> I think it should dump the user data portion, especially since that
>> matches what pg_dump would do if you did not specify the table or schema.
>
> +1
>
> If you don't have time slots to fix that by then, I will have a look at
> fixing that while in beta.

Here is a patch against 9.1. If there is agreement with the approach
I'll redo for 9.2 and git head and apply.

Joe

--
Joe Conway
credativ LLC: http://www.credativ.us
Linux, PostgreSQL, and general Open Source
Training, Service, Consulting, & 24x7 Support

Attachment Content-Type Size
pg_dump_ext_obj.diff text/x-patch 2.6 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2013-03-15 02:25:53 Assertion failure when promoting node by deleting recovery.conf and restart node
Previous Message Boszormenyi Zoltan 2013-03-14 23:48:04 Re: Re: Proposal for Allow postgresql.conf values to be changed via SQL [review]