Re: Pgoutput not capturing the generated columns

[Rajendra Kumar Dangwal]

Hi PG Hackers.

We are interested in enhancing the functionality of the pgoutput plugin by 
adding support for generated columns. 
Could you please guide us on the necessary steps to achieve this? Additionally, 
do you have a platform for tracking such feature requests? Any insights or 
assistance you can provide on this matter would be greatly appreciated.

Many thanks.
Rajendra.

Re: Pgoutput not capturing the generated columns

[Rajendra Kumar Dangwal]

Thanks Euler,
Greatly appreciate your inputs.

> Should pgoutput provide a complete row? Probably. If it is an option that 
> defaults to false and doesn't impact performance.

Yes, it would be great if this feature can be implemented.

> The logical replication design decides to compute the generated columns at 
> subscriber side.

If I understand correctly, this approach involves establishing a function on 
the subscriber's side that emulates the operation executed to derive the 
generated column values.
If yes, I see one potential issue where disparities might surface between the 
values of generated columns on the subscriber's side and those computed within 
Postgres. This could happen if the generated column's value relies on the 
current_time function.

Please let me know how can we track the feature requests and the discussions 
around that.

Thanks,
Rajendra.

Pgoutput not capturing the generated columns

[Rajendra Kumar Dangwal]

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.