Horton

Re: Minimal logical decoding on standbys

Bertrand Drouvot <bertranddrouvot.pg@gmail.com>

View thread
From: "Drouvot, Bertrand" <bertranddrouvot.pg@gmail.com>
To: Amit Kapila <amit.kapila16@gmail.com>
Cc: Alvaro Herrera <alvherre@alvh.no-ip.org>, Jeff Davis <pgsql@j-davis.com>, Andres Freund <andres@anarazel.de>, Robert Haas <robertmhaas@gmail.com>, Thomas Munro <thomas.munro@gmail.com>, Ibrar Ahmed <ibrar.ahmad@gmail.com>, Amit Khandekar <amitdkhan.pg@gmail.com>, fabriziomello@gmail.com, tushar <tushar.ahuja@enterprisedb.com>, Rahila Syed <rahila.syed@2ndquadrant.com>, pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2023-04-06T13:02:26Z
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 →

  1. Reduce the log level in 035_standby_logical_decoding.pl.

  2. 035_standby_logical_decoding: Add missing waits for replication

  3. For cascading replication, wake physical and logical walsenders separately

  4. Handle logical slot conflicts on standby

  5. Support invalidating replication slots due to horizon and wal_level

  6. Prevent use of invalidated logical slot in CreateDecodingContext()

  7. Replace replication slot's invalidated_at LSN with an enum

  8. Pass down table relation into more index relation functions

  9. Assert only valid flag bits are passed to visibilitymap_set()

  10. Remove unused _bt_delitems_delete() argument.

  11. Add xl_btree_delete optimization.

Hi,

On 4/6/23 7:59 AM, Amit Kapila wrote:
> On Wed, Apr 5, 2023 at 6:14 PM Drouvot, Bertrand
> <bertranddrouvot.pg@gmail.com> wrote:
>>
>> On 4/5/23 12:28 PM, Amit Kapila wrote:
>>> On Wed, Apr 5, 2023 at 2:41 PM Drouvot, Bertrand
>>> <bertranddrouvot.pg@gmail.com> wrote:
>>>> Maybe we could change the doc with something among those lines instead?
>>>>
>>>> "
>>>> Existing logical slots on standby also get invalidated if wal_level on primary is reduced to
>>>> less than 'logical'. This is done as soon as the standby detects such a change in the WAL stream.
>>>>
>>>> It means, that for walsenders that are lagging (if any), some WAL records up to the parameter change on the
>>>> primary won't be decoded".
>>>>
>>>> I don't know whether this is what one would expect but that should be less of a surprise if documented.
>>>>
>>>> What do you think?
>>>>
>>>
>>> Yeah, I think it is better to document to avoid any surprises if
>>> nobody else sees any problem with it.
>>
>> Ack.
>>
> 
> This doesn't seem to be addressed in the latest version.

Right, I was waiting if "nobody else sees any problem with it".

Added it now in V62 posted up-thread.

> And today, I
> think I see one more point about this doc change:
> +    <para>
> +     A logical replication slot can also be created on a hot standby.
> To prevent
> +     <command>VACUUM</command> from removing required rows from the system
> +     catalogs, <varname>hot_standby_feedback</varname> should be set on the
> +     standby. In spite of that, if any required rows get removed, the slot gets
> +     invalidated. It's highly recommended to use a physical slot
> between the primary
> +     and the standby. Otherwise, hot_standby_feedback will work, but
> only while the
> +     connection is alive (for example a node restart would break it). Existing
> +     logical slots on standby also get invalidated if wal_level on
> primary is reduced to
> +     less than 'logical'.
> 
> If hot_standby_feedback is not set then can logical decoding on
> standby misbehave? If so, that is not very clear from this doc change
> if that is acceptable.

I don't think it would misbehave but that primary may delete system catalog rows
that could be needed by the logical decoding on the standby (as it does not know about the
catalog_xmin on the standby).

Added this remark in V62.

Regards,

-- 
Bertrand Drouvot
PostgreSQL Contributors Team
RDS Open Source Databases
Amazon Web Services: https://aws.amazon.com