From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | depesz(at)depesz(dot)com |
Cc: | Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_dump -s dumps data?! |
Date: | 2012-01-30 16:30:51 |
Message-ID: | 15810.1327941051@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
hubert depesz lubaczewski <depesz(at)depesz(dot)com> writes:
> On Mon, Jan 30, 2012 at 11:12:09AM -0500, Tom Lane wrote:
>> What tests were those exactly? I'm not aware of any agreed changes in
>> this area.
> 1. create table with extension
> 2. try to dump it's content with pg_dump
> 3. try to dump schema of database
> 4. try to dump schema of another table (not from extension)
> 5. drop extension, load another extension, this time, with marking table
> with pg_extension_config_dump
> repeat steps 2,3,4.
That is way too vague for my taste, as you have not shown the pg_dump
options you're using, for example.
> the way pg works in git HEAD is much more sensible.
I'm not aware that the way it works has been changed intentionally,
so if you're seeing a difference here it's more likely that a bug has
been added than removed. Please provide an exact test case.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Angelico | 2012-01-30 16:39:07 | Re: Lock/deadlock issues with priority queue in Postgres - possible VACUUM conflicts |
Previous Message | hubert depesz lubaczewski | 2012-01-30 16:25:54 | Re: pg_dump -s dumps data?! |
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Janes | 2012-01-30 16:48:51 | Re: Group commit, revised |
Previous Message | hubert depesz lubaczewski | 2012-01-30 16:25:54 | Re: pg_dump -s dumps data?! |