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 20191210180821.GA12847@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-10, Tomas Vondra wrote:

> On Tue, Dec 10, 2019 at 09:42:17AM +0900, Kyotaro Horiguchi wrote:
> > At Tue, 10 Dec 2019 00:44:09 +0100, Tomas Vondra <tomas.vondra@2ndquadrant.com> wrote in

> > I'm not sure how much xact_start for walsender is useful and we really
> > is not running a statement there.  Also autovac launcher starts
> > transaction without a valid statement timestamp perhaps for the same
> > reason.
> 
> Maybe, but then maybe we should change it so that we don't report any
> timestamps for such processes.

Yeah, I think we should to that.

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



pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Contention on LWLock buffer_content, due to SHARED lock(?)
Next
From: Robert Haas
Date:
Subject: Re: disable only nonparallel seq scan.