Re: Minimal logical decoding on standbys

bdrouvotAWS <bdrouvot@amazon.com>

From: "Drouvot, Bertrand" <bdrouvot@amazon.com>

To: <fabriziomello@gmail.com>

Cc: Alvaro Herrera <alvherre@2ndquadrant.com>, Andres Freund <andres@anarazel.de>, tushar <tushar.ahuja@enterprisedb.com>, "[pgdg] Robert Haas" <robertmhaas@gmail.com>, Amit Khandekar <amitdkhan.pg@gmail.com>, Rahila Syed <rahila.syed@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>

Date: 2021-04-06T12:30:29Z

Lists: pgsql-hackers

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Reduce the log level in 035_standby_logical_decoding.pl.
- 3034dc56ef4b 16.0 landed
035_standby_logical_decoding: Add missing waits for replication
- 57411c82ce86 16.0 landed
For cascading replication, wake physical and logical walsenders separately
- e101dfac3a53 16.0 landed
Handle logical slot conflicts on standby
- 26669757b6a7 16.0 landed
Support invalidating replication slots due to horizon and wal_level
- be87200efd93 16.0 landed
Prevent use of invalidated logical slot in CreateDecodingContext()
- 4397abd0a2af 16.0 landed
Replace replication slot's invalidated_at LSN with an enum
- 15f8203a5975 16.0 landed
Pass down table relation into more index relation functions
- 61b313e47eb9 16.0 landed
Assert only valid flag bits are passed to visibilitymap_set()
- a88a18b1250b 16.0 landed
Remove unused _bt_delitems_delete() argument.
- dc43492e46c7 14.0 cited
Add xl_btree_delete optimization.
- d2e5e20e5711 13.0 cited

Attachments

v15-0005-Doc-changes-describing-details-about-logical-dec.patch (text/plain) patch v15-0005
v15-0004-New-TAP-test-for-logical-decoding-on-standby.patch (text/plain) patch v15-0004
v15-0003-Handle-logical-slot-conflicts-on-standby.patch (text/plain) patch v15-0003
v15-0002-Add-info-in-WAL-records-in-preparation-for-logic.patch (text/plain) patch v15-0002
v15-0001-Allow-logical-decoding-on-standby.patch (text/plain) patch v15-0001

Hi,

On 3/25/21 8:51 AM, Drouvot, Bertrand wrote:
>
>
> On 3/25/21 12:01 AM, Fabrízio de Royes Mello wrote:
>>
>>
>> On Wed, Mar 24, 2021 at 3:57 AM Drouvot, Bertrand 
>> <bdrouvot@amazon.com <mailto:bdrouvot@amazon.com>> wrote:
>> >
>> > Thanks for pointing out, fixed in v14 attached.
>> >
>>
>> Thanks... now everything is working as expected... changed the status 
>> to Ready for Commiter:
>> https://commitfest.postgresql.org/32/2968/ 
>> <https://commitfest.postgresql.org/32/2968/>
>>
> Thanks!
>
> I think this would be a great feature, so I am looking forward to 
> help/work on any comments/suggestions that they may have.
>
Just needed a minor rebase due to 2 new conflicts with:

  * b4af70cb21: in vacuum_log_cleanup_info() (see new
    v15-0002-Add-info-in-WAL-records-in-preparation-for-logic.patch)
  * 43620e3286: oid conflict with pg_log_backend_memory_contexts() and
    pg_stat_get_db_conflict_snapshot() (see new
    v15-0003-Handle-logical-slot-conflicts-on-standby.patch)

New v15 attached is passing "make check" and the 2 new associated TAP tests.

Bertrand