Re: Column Filtering in Logical Replication
| От | Amit Kapila |
|---|---|
| Тема | Re: Column Filtering in Logical Replication |
| Дата | |
| Msg-id | CAA4eK1+f-wsbd5jnpDXE9hS9OfG2_Xb++2R+KZ3VQ3=9RJwThg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: Column Filtering in Logical Replication (Alvaro Herrera <alvherre@alvh.no-ip.org>) |
| Ответы |
Re: Column Filtering in Logical Replication
|
| Список | pgsql-hackers |
On Mon, Jan 3, 2022 at 8:01 PM Alvaro Herrera <alvherre@alvh.no-ip.org> wrote:
>
fetch_remote_table_info()
{
..
+ appendStringInfo(&cmd,
+ " SELECT pg_catalog.unnest(prattrs)\n"
+ " FROM pg_catalog.pg_publication p JOIN\n"
+ " pg_catalog.pg_publication_rel pr ON (p.oid = pr.prpubid)\n"
+ " WHERE p.pubname IN (%s) AND\n",
+ publications.data);
+ if (!am_partition)
+ appendStringInfo(&cmd, "prrelid = %u", lrel->remoteid);
+ else
+ appendStringInfo(&cmd,
+ "prrelid IN (SELECT relid\n"
+ " FROM pg_catalog.pg_partition_tree(pg_catalog.pg_partition_root(%u)))",
+ lrel->remoteid);
IIUC, this doesn't deal with cases when some publication has not
specified table attrs. In those cases, I think it should return all
attrs? Also, it is not very clear to me what exactly we want to do
with partitions?
--
With Regards,
Amit Kapila.
В списке pgsql-hackers по дате отправления: