Re: row filtering for logical replication

Mon, 04 Jan 2021 05:38:07 -0800 

Hi Masahiko,


>
> You sent in your patch to pgsql-hackers on Dec 17, but you did not
> post it to the next CommitFest[1] (I found the old entry of this
> patch[2] but it's marked as "Returned with feedback"). If this was
> intentional, then you need to take no action.  However, if you want
> your patch to be reviewed as part of the upcoming CommitFest, then you
> need to add it yourself before 2021-01-01 AoE[3]. Thanks for your
> contributions.
>
>
Thanks for letting me know of this, I added this patch to the next commit
fest before 2021-01-01 AoE[3].

I'm also attaching the updated commits so that the tests pass on the CI.

Thanks,
Onder KALACI
Software Engineer at Microsoft &
Developing the Citus database extension for PostgreSQL

Attachment: 0001-Subject-PATCH-1-8-Remove-unused-atttypmod-column-fro.patch
Description: Binary data

Attachment: 0004-Subject-PATCH-4-8-Rename-a-WHERE-node.patch
Description: Binary data

Attachment: 0002-Subject-PATCH-2-8-Store-number-of-tuples-in-WalRcvEx.patch
Description: Binary data

Attachment: 0003-Subject-PATCH-3-8-Refactor-function-create_estate_fo.patch
Description: Binary data

Attachment: 0005-Subject-PATCH-5-8-Row-filtering-for-logical-replicat.patch
Description: Binary data

Attachment: 0006-Subject-PATCH-6-8-Print-publication-WHERE-condition-.patch
Description: Binary data

Attachment: 0007-Publication-where-condition-support-for-pg_dump.patch
Description: Binary data

Attachment: commands_to_perf_test.sql
Description: Binary data

Reply via email to