Horton
Menu

Re: speedup COPY TO for partitioned table.

Kirill Reshke <reshkekirill@gmail.com>

View thread
From: Kirill Reshke <reshkekirill@gmail.com>
To: jian he <jian.universality@gmail.com>
Cc: vignesh C <vignesh21@gmail.com>, David Rowley <dgrowleyml@gmail.com>, Melih Mutlu <m.melihmutlu@gmail.com>, PostgreSQL Hackers <pgsql-hackers@lists.postgresql.org>
Date: 2025-04-07T16:54:13Z
Lists: pgsql-hackers 
On Fri, 4 Apr 2025, 15:17 Kirill Reshke, <reshkekirill@gmail.com> wrote:

> Hi!
>
> First of all, a commit message does not need to contain SQL examples
> of what it does. We should provide human-readable explanations and
> that's it.
>
> Next, about changes to src/test/regress/sql/copy2.sql. I find the sql
> you used to test really unintuitive. How about CREATE TABLE ...
> PARTITION OF syntax? It is also one command instead of two (create +
> alter). It is also hard to say what partition structure is, because
> column names on different partition levels are the same, just order is
> switched. Let's change it to something more intuitive too?
>
>
>
> --
> Best regards,
> Kirill Reshke
>

Maybe we can tab-complete here if prefix matches pg_% ? Does that makes
good use case?

>

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

  1. Support COPY TO for partitioned tables.

  2. Re-implement the ereport() macro using __VA_ARGS__.