On Wed, Apr 24, 2024 at 4:35 PM Michael Paquier <mich...@paquier.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.
