| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: reload-through-the-top-parent switch the partition table |
| Date: | 2017-08-03 14:43:25 |
| Message-ID: | CA+TgmoaZ5kymbyyz=p9fkZKyWNH66QRNeNq_w82XzqYw+qArbA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Aug 2, 2017 at 4:08 PM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> On 8/2/17 13:58, Tom Lane wrote:
>> I notice that the option list already includes some references to
>> "insert", so maybe "--insert-via-partition-root"? Although you could
>> argue that that's confusing when we're using COPY.
>
> "load" could be more general. But I'm also OK with "restore".
"load" seems better than "restore" to me, both because it's shorter
and because it sounds less like pg_dump will be doing the job of
pg_restore.
So maybe --load-via-partition-root if nobody likes my previous
suggestion of --partition-data-via-root ?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2017-08-03 14:45:50 | Re: intermittent failures in Cygwin from select_parallel tests |
| Previous Message | Robert Haas | 2017-08-03 14:41:42 | Re: reload-through-the-top-parent switch the partition table |