Re: Restrict publishing of partitioned table with a foreign table as partition - Mailing list pgsql-hackers

From Álvaro Herrera
Subject Re: Restrict publishing of partitioned table with a foreign table as partition
Date
Msg-id 202504071230.2dw72naygjvf@alvherre.pgsql
Whole thread Raw
In response to Re: Restrict publishing of partitioned table with a foreign table as partition  (Sergey Tatarintsev <s.tatarintsev@postgrespro.ru>)
List pgsql-hackers
On 2025-Apr-07, Sergey Tatarintsev wrote:

> I think this is a wrong assumption:
> 
> ScanKeyInit(&key[keycount++], Anum_pg_class_relispartition,
> BTEqualStrategyNumber, F_BOOLEQ, BoolGetDatum(false));
> 
> In this case sch5.part1 is partitioned table, but it also partition of table
> in different schema

Yeah, this looks ill-considered.

After looking at this code some more, I'm withdrawing myself from here.
(I don't mean just this patch in particular, I mean the logical
replication code as a whole.)

Thanks,

-- 
Álvaro Herrera               48°01'N 7°57'E  —  https://www.EnterpriseDB.com/
"La persona que no quería pecar / estaba obligada a sentarse
 en duras y empinadas sillas    / desprovistas, por cierto
 de blandos atenuantes"                          (Patricio Vogel)



pgsql-hackers by date:

Previous
From: Mahendra Singh Thalor
Date:
Subject: as per commit 643a1a61985bef2590496, move create/open dir code to function using switch case of pg_backup_directory.c file also
Next
From: Álvaro Herrera
Date:
Subject: Re: Restrict publishing of partitioned table with a foreign table as partition