From: | Rajendra Kumar Dangwal <dangwalrajendra888(at)gmail(dot)com> |
---|---|
To: | pgsql-hackers(at)lists(dot)postgresql(dot)org |
Subject: | Pgoutput not capturing the generated columns |
Date: | 2023-08-01 06:47:33 |
Message-ID: | B80D17B2-2C8E-4C7D-87F2-E5B4BE3C069E@gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi PG Users.
We are using Debezium to capture the CDC events into Kafka.
With decoderbufs and wal2json plugins the connector is able to capture the generated columns in the table but not with pgoutput plugin.
We tested with the following example:
CREATE TABLE employees (
id SERIAL PRIMARY KEY,
first_name VARCHAR(50),
last_name VARCHAR(50),
full_name VARCHAR(100) GENERATED ALWAYS AS (first_name || ' ' || last_name) STORED
);
// Inserted few records when the connector was running
Insert into employees (first_name, last_name) VALUES ('ABC' , 'XYZ’);
With decoderbufs and wal2json the connector is able to capture the generated column `full_name` in above example. But with pgoutput the generated column was not captured.
Is this a known limitation of pgoutput plugin? If yes, where can we request to add support for this feature?
Thanks.
Rajendra.
From | Date | Subject | |
---|---|---|---|
Next Message | Kyotaro Horiguchi | 2023-08-01 06:59:12 | Re: Incorrect handling of OOM in WAL replay leading to data loss |
Previous Message | Kyotaro Horiguchi | 2023-08-01 06:46:55 | Re: Fix compilation warnings when CFLAGS -Og is specified |