Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On Mon, Jan 27, 2025 at 07:13:01AM +, Bertrand Drouvot wrote: > On Fri, Jan 24, 2025 at 02:44:21PM -0500, Andres Freund wrote: > > If we could trigger VACUUM in a transaction on the primary this would be > > easy, but we can't. > > Another idea that I had ([1]) was to make use of injecti

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On Mon, Jan 27, 2025 at 09:28:57AM -0500, Tom Lane wrote: > Bertrand Drouvot writes: > > On Fri, Jan 24, 2025 at 11:42:15AM -0500, Tom Lane wrote: > >> PS: FTR, the hits I got on this in the past 90 days were > >> > >> sysname |branch | snapshot | stage |

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Bertrand Drouvot writes: > On Fri, Jan 24, 2025 at 11:42:15AM -0500, Tom Lane wrote: >> PS: FTR, the hits I got on this in the past 90 days were >> >> sysname |branch | snapshot | stage | >>l

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On Fri, Jan 24, 2025 at 11:42:15AM -0500, Tom Lane wrote: > I realized just now that drongo has been intermittently failing like this: Thanks for the report! > PS: FTR, the hits I got on this in the past 90 days were > > sysname |branch | snapshot | stage |

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On Fri, Jan 24, 2025 at 02:44:21PM -0500, Andres Freund wrote: > Hm, maybe I'm missing something, but isn't it possible for the active slot to > actually progress decoding past the conflict point? It's an active slot, with > the consumer running in the background, so all that needs to happen f

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On 2025-01-24 14:56:45 -0500, Tom Lane wrote: > Alexander Lakhin writes: > > There is also a reference to a discussion of the failure there: > > https://www.postgresql.org/message-id/657815a2-5a89-fcc1-1c9d-d77a6986b...@gmail.com > > (In short, I observed that that test suffers from bgwriter'

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Alexander Lakhin writes: > There is also a reference to a discussion of the failure there: > https://www.postgresql.org/message-id/657815a2-5a89-fcc1-1c9d-d77a6986b...@gmail.com > (In short, I observed that that test suffers from bgwriter's activity.) Hmm, that's an interesting theory, but it fai

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On 2025-01-24 21:00:00 +0200, Alexander Lakhin wrote: > 24.01.2025 18:42, Tom Lane wrote: > > I realized just now that drongo has been intermittently failing like this: > > > > 147/256 postgresql:recovery / recovery/035_standby_logical_decoding > > ERROR 2116.16s (ex

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, On 2025-01-24 14:23:26 -0500, Andres Freund wrote: > On 2025-01-24 11:42:15 -0500, Tom Lane wrote: > There's a failure before this one: > [05:23:54.643](0.013s) not ok 23 - activeslot slot invalidation is logged > with vacuum on pg_class > > > > This has been happening for some time, in all t

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hi, Thanks for noticing the pattern. On 2025-01-24 11:42:15 -0500, Tom Lane wrote: > I realized just now that drongo has been intermittently failing like this: > > 147/256 postgresql:recovery / recovery/035_standby_logical_decoding > ERROR 2116.16s (exit status 255 or si

Re: BF member drongo doesn't like 035_standby_logical_decoding.pl

Hello Tom, 24.01.2025 18:42, Tom Lane wrote: I realized just now that drongo has been intermittently failing like this: 147/256 postgresql:recovery / recovery/035_standby_logical_decoding ERROR 2116.16s (exit status 255 or signal 127 SIGinvalid) ---

BF member drongo doesn't like 035_standby_logical_decoding.pl

I realized just now that drongo has been intermittently failing like this: 147/256 postgresql:recovery / recovery/035_standby_logical_decoding ERROR 2116.16s (exit status 255 or signal 127 SIGinvalid) - 8< --