Re: pg_dump gets attributes from tables in extensions - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: pg_dump gets attributes from tables in extensions
Date
Msg-id 20150224145555.GH5169@alvh.no-ip.org
Whole thread Raw
In response to Re: pg_dump gets attributes from tables in extensions  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: pg_dump gets attributes from tables in extensions
List pgsql-hackers
Michael Paquier wrote:
> On Tue, Feb 24, 2015 at 3:13 PM, Rushabh Lathia <rushabh.lathia@gmail.com>
> wrote:

> > rushabh@rushabh-centos-vm:dump_test$ cat dump_test--1.0.sql
> > /* dump_test/dump_test--1.0.sql */

Hm.  I think it would be a good idea to collect these extension files
somewhere so that pg_dump hacking can be tested with them.  Right now,
the extension part of pg_dump is easy to break in subtle ways, which
discourages anyone who wants to meddle with it.

Maybe something in src/test/modules could keep these files so that
pg_dump can be tested.  Is anybody interested in doing that?

> Btw, perhaps you may have noticed, but I marked this patch as rejected... I
> don't think it makes much sense to put restrictions in this code path after
> finding my way through all the stuff of pg_dump.

Please don't do that -- I mean don't use the commitfest app as the only
source for random bits of data.  If you want to reject a patch, please
make sure to point that out in the email thread.  It's impossible to go
from email archives to commitfest entries.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tomas Vondra
Date:
Subject: Re: KNN-GiST with recheck
Next
From: Ryan Pedela
Date:
Subject: Re: deparsing utility commands