| From: | Nathan Bossart <nathandbossart(at)gmail(dot)com> |
|---|---|
| To: | Melih Mutlu <m(dot)melihmutlu(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: speedup COPY TO for partitioned table. |
| Date: | 2025-01-27 20:30:17 |
| Message-ID: | Z5fs2RFocT0Epbcf@nathan |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 22, 2025 at 01:54:32AM +0300, Melih Mutlu wrote:
> I confirm that the patch introduces some improvement in simple cases like
> the one you shared. I looked around a bit to understand whether there is an
> obvious reason why copying from a partitioned table is not allowed, but
> couldn't find one. It seems ok to me.
From the original discussion [0], it seems like it was considered a
nonessential part of an otherwise massive patch set. Perhaps it's time to
revisit it.
[0] https://postgr.es/m/CAA4eK1LqTqZkPSoonF5_cOz94OUZG9j0PNfLdhi_nPtW82fFVA%40mail.gmail.com
--
nathan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2025-01-27 20:38:39 | Re: Disabling vacuum truncate for autovacuum |
| Previous Message | Vladimir Vasilenko | 2025-01-27 20:22:55 | How to build Postgres Pro on FreeBSD? |