pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Tomas Vondra <tomas.vondra@enterprisedb.com>
To: Amit Kapila <amit.kapila16@gmail.com>
To: houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>
Cc: Justin Pryzby <pryzby@telsasoft.com>
Cc: Rahila Syed <rahilasyed90@gmail.com>
Cc: Peter Smith <smithpb2250@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Cc: shiy.fnst@fujitsu.com <shiy.fnst@fujitsu.com>
Subject: Re: Column Filtering in Logical Replication
Date: Thu, 17 Mar 2022 20:17:55 +0100
Message-ID: <f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com> (raw )
In-Reply-To: <f217341d-6841-390d-3dd2-89f9d1de17fe@enterprisedb.com >
References: <202201120041.p24wvsfcsope@alvherre.pgsql >
<d26d24dd-2fab-3c48-0162-2b7f84a9c893@enterprisedb.com >
<CAA4eK1JJ5qgqbjfYQU9F4R1+OABxec-DQechQXus0fanDjaAVg@mail.gmail.com >
<OS0PR01MB571614E4A39DD33669D5AFD6940A9@OS0PR01MB5716.jpnprd01.prod.outlook.com >
<e4b0fb99-3d74-7333-1e71-74f990b641ee@enterprisedb.com >
<78b8d385-57cb-9a3f-cfe5-9f300f15eced@enterprisedb.com >
<822a8e40-287c-59ff-0ea9-35eb759f4fe6@enterprisedb.com >
<CAA4eK1J9UDnM-xN7viu4eO_DDL_PqMG9F6ZsskqEU7snujXi+A@mail.gmail.com >
<2b8471f9-3849-c91f-ef82-9181d4bca0a7@enterprisedb.com >
<CAA4eK1KUpOnFam+2bBuGGX-_pZbmO_ShJV6G=GT-RyM7gQSvWg@mail.gmail.com >
<16e83ce3-8415-b732-37b2-c3329a2c13a1@enterprisedb.com >
<OS0PR01MB57164514E1DE1E579B0B6C46940F9@OS0PR01MB5716.jpnprd01.prod.outlook.com >
<CAA4eK1KvFAygPbFu=cUvnqhmTLPpjzqp8p4UNSsLkiZmvFp8oQ@mail.gmail.com >
<bc6918cc-2025-6c91-2ca4-c237af67e97d@enterprisedb.com >
<f217341d-6841-390d-3dd2-89f9d1de17fe@enterprisedb.com >
I pushed the second fix. Interestingly enough, wrasse failed in the
013_partition test. I don't see how that could be caused by this
particular commit, though - see the pgsql-committers thread [1].
I'd like to test & polish the main patch over the weekend, and get it
committed early next week. Unless someone thinks it's definitely not
ready for that ...
[1]
https://www.postgresql.org/message-id/E1nUsch-0008rQ-FW%40gemulon.postgresql.org
--
Tomas Vondra
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
view thread (257+ messages) latest in thread
Message-ID: <f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com>
Permalink: ../f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com/
Also on: postgresql.org/message-id/f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com
copy link · copy postgr.es
reply Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: tomas.vondra@enterprisedb.com, amit.kapila16@gmail.com, houzj.fnst@fujitsu.com, peter.eisentraut@enterprisedb.com, alvherre@alvh.no-ip.org, pryzby@telsasoft.com, rahilasyed90@gmail.com, smithpb2250@gmail.com, shiy.fnst@fujitsu.com
Subject: Re: Column Filtering in Logical Replication
In-Reply-To: <f90d2b03-4462-ce95-a524-d91464e797c8@enterprisedb.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox