From: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
---|---|
To: | Michael Paquier <michael(at)paquier(dot)xyz> |
Cc: | Nathan Bossart <nathandbossart(at)gmail(dot)com>, Postgres hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Partitioned tables and [un]loggedness |
Date: | 2024-04-24 23:43:58 |
Message-ID: | CAKFQuwZwMOkw-7112u1-gXEhRWuXiZe9otp801Z3dPVvarKdsA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Apr 24, 2024 at 4:35 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
>
> I disagree here, actually. Temporary tables are a different beast
> because they require automated cleanup which would include interacting
> with the partitionining information if temp and non-temp relations are
> mixed. That's why the current restrictions are in place: you should
>
[ not ] ?
> be able to mix them.
>
My point is that if you feel that treating logged as a copy-able property
is OK then doing the following should also just work:
postgres=# create temp table parentt ( id integer ) partition by range (id);
CREATE TABLE
postgres=# create table child10t partition of parentt for values from (0)
to (9);
ERROR: cannot create a permanent relation as partition of temporary
relation "parentt"
i.e., child10t should be created as a temporary partition under parentt.
David J.
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2024-04-24 23:44:41 | Re: Partitioned tables and [un]loggedness |
Previous Message | Michael Paquier | 2024-04-24 23:36:15 | Re: Improve WALRead() to suck data directly from WAL buffers when possible |