RE: [PATCH] Fix stale relation close in sequence synchronization - Mailing list pgsql-hackers

From Hayato Kuroda (Fujitsu)
Subject RE: [PATCH] Fix stale relation close in sequence synchronization
Date
Msg-id OS9PR01MB121492298361AC9CF08AF93B2F5372@OS9PR01MB12149.jpnprd01.prod.outlook.com
Whole thread
In response to [PATCH] Fix stale relation close in sequence synchronization  (Ayush Tiwari <ayushtiwari.slg01@gmail.com>)
Responses Re: [PATCH] Fix stale relation close in sequence synchronization
List pgsql-hackers
Dear Ayush,

> I found a crash in the logical replication sequence synchronization worker
> when the publisher returns NULL sequence data for a sequence after at least
> one sequence in the same sync batch has already been processed.

Good catch. I confirmed the HEAD can crash with your added test.

> The attached patch clears the output Relation pointer at the start of
> get_and_validate_seq_info() and clears the local pointer in copy_sequences()
> after closing it. That keeps early returns from reusing a relation from a
> previous row.

To confirm; can't we declare the sequence_rel in the inner-loop? My first
impression was the bug caused by the wrong lifetime. Are there any other
thoughts around here?

Added Vignesh in CC because he was a primary author.

Best regards,
Hayato Kuroda
FUJITSU LIMITED


pgsql-hackers by date:

Previous
From: shveta malik
Date:
Subject: Re: Include schema-qualified names in publication error messages.
Next
From: Ayush Tiwari
Date:
Subject: Re: [PATCH] Fix stale relation close in sequence synchronization