Ashwin Agrawal

We have not supported logical decoding/replication yet in GPDB, hence failures from trying to get changes from logical slot to seem reasonable. **I think as an interim step we should...

Please hold from merging this PR. I will try to dig some context around this behavior change and lets discuss it fully to understand downside or not before loosing out...

Ignore the below post, things are working fine `gp_ao_or_aocs_seg()` only reports QDs state, and that caused the confusion. When manually running select * pg_aoseg table to look at segments value...

@l-wang what's the plan for this PR, taking it forward to completion or not more required?

Given we ship with quicklz we do need coverage for it. So, we should try to complete this PR and ship it. Lets try to trace out what's remaining to...

Started to review this PR. Will try to provide most of my comments by this week.

Confirming problem still exists in lastest GPDB6. We should explore the fix proposed above by Asim.

Just for reference this topic was also discussed in mailing list [thread](https://groups.google.com/a/greenplum.org/g/gpdb-dev/c/Utt1uXGEQGE/m/p_HbbeQoAAAJ).

Also, this issue is duplicate of https://github.com/greenplum-db/gpdb/issues/9060

For long term, just throwing out there maybe need to rename those 2 columns in gp_segment_configuration to something which clearly communicate the purpose and usage. Specially `address` column is very...