From: | Ron <ronljohnsonjr(at)gmail(dot)com> |
---|---|
To: | "pgsql-general(at)postgresql(dot)org >> PG-General Mailing List" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_dump of partitioned table not working. |
Date: | 2020-12-03 01:51:00 |
Message-ID: | cb7433a1-b0e1-ab51-1b26-35d949882f54@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 12/2/20 6:14 PM, Ron wrote:
> On 12/2/20 5:50 PM, Tom Lane wrote:
>> I wrote:
>>> What you need here is something like "pg_dump -t measurement*"
>>> to indicate that you want measurement's child tables too, but
>>> AFAIR pg_dump has no such feature. Maybe we should add it.
>> Or actually: that syntax does do something, but it selects
>> tables by pattern matching not hierarchy, ie you get everything
>> whose name starts with "measurement". Depending on your naming
>> conventions, that might be close enough.
>>
>> It does seem like there might be reason to have a switch along
>> the lines of "--include-child-tables".
>
> That would be great, but won't help me in v12.
To clarify: I'm not being sarcastic. Such a feature really would be useful.
--
Angular momentum makes the world go 'round.
From | Date | Subject | |
---|---|---|---|
Next Message | charles meng | 2020-12-03 06:53:35 | Alter the column data type of the large data volume table. |
Previous Message | Ron | 2020-12-03 01:39:35 | Re: pg_dump of partitioned table not working. |