From: | Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Stephen Frost <sfrost(at)snowman(dot)net> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: pg_dump emits ALTER TABLE ONLY partitioned_table |
Date: | 2017-02-20 04:05:28 |
Message-ID: | 2509e5e9-4de2-1846-ddd0-6964f81d6c8b@lab.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi Stephen,
On 2017/02/17 22:32, Stephen Frost wrote:
> Amit,
>
> * Amit Langote (Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp) wrote:
>> In certain cases, pg_dump's dumpTableSchema() emits a separate ALTER TABLE
>> command for those schema elements of a table that could not be included
>> directly in the CREATE TABLE command for the table.
>
> Any chance we could start adding regression tests for how pg_dump
> handles partitions? I'm just about to the point where I have pretty
> much everything else covered (at least in pg_dump.c, where it's not a
> hard-to-reproduce error/exit case, or something version-dependent).
>
> If you have any questions about how the TAP tests for pg_dump work, or
> about how to generate code-coverage checks to make sure you're at least
> hitting every line (tho, of course, not every possible path), let me
> know. I'd be happy to explain them.
Yeah, I guess it would be a good idea to have some pg_dump TAP test
coverage for the new partitioning stuff. I will look into that and get
back to you if I don't grok something there.
Thanks,
Amit
From | Date | Subject | |
---|---|---|---|
Next Message | Devrim Gündüz | 2017-02-20 04:33:32 | Re: drop support for Python 2.3 |
Previous Message | Tom Lane | 2017-02-20 04:02:53 | Re: Adding new output parameter of pg_stat_statements to identify operation of the query. |