Re: xact_start for walsender & logical decoding not updated - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: xact_start for walsender & logical decoding not updated
Date
Msg-id 20200107211717.GA20056@alvherre.pgsql
Whole thread Raw
In response to Re: xact_start for walsender & logical decoding not updated  (Tomas Vondra <tomas.vondra@2ndquadrant.com>)
Responses Re: xact_start for walsender & logical decoding not updated
List pgsql-hackers
On 2019-Dec-29, Tomas Vondra wrote:

> On Fri, Dec 27, 2019 at 04:46:18PM -0300, Alvaro Herrera wrote:
> > 
> > This patch changes xact.c to avoid updating transaction start timestamps
> > for walsenders (maybe more commentary is desirable).  I think logical
> > decoding is just a special form of walsender and thus it would also be
> > updated by this patch, unless I misunderstood what Tomas explained.
> > 
> 
> It's true walsender should not be doing any read-write transactions or
> executing statements (well, maybe a decoding plugin could, but using
> historic snapshot).
> 
> So I agree not leaving xact_start for walsender processes seems OK.

OK, I pushed my patch to branches 10 - master.
(See https://postgr.es/m/20200107211624.GA18974@alvherre.pgsql )

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCH] Atomic pgrename on Windows
Next
From: Stephen Frost
Date:
Subject: Re: Removing pg_pltemplate and creating "trustable" extensions