Re: Pruning never visible changes - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Pruning never visible changes
Date
Msg-id CANbhV-HTEzcwhrGEc=Kh_Nkbqi7J3SxLy9Ed2a=tTc4N-svmeQ@mail.gmail.com
Whole thread Raw
In response to Re: Pruning never visible changes  (Laurenz Albe <laurenz.albe@cybertec.at>)
List pgsql-hackers
On Fri, 16 Sept 2022 at 21:07, Laurenz Albe <laurenz.albe@cybertec.at> wrote:
>
> On Fri, 2022-09-16 at 10:26 -0400, Tom Lane wrote:
> > Simon Riggs <simon.riggs@enterprisedb.com> writes:
> > > A user asked me whether we prune never visible changes, such as
> > > BEGIN;
> > > INSERT...
> > > UPDATE.. (same row)
> > > COMMIT;
> >
> > Didn't we just have this discussion in another thread?
>
> For reference: that was
> https://postgr.es/m/f6a491b32cb44bb5daaafec835364f7149348fa1.camel@cybertec.at

Thanks. I confirm I hadn't seen that, and indeed, I wrote the patch on
5 Sept before you posted.

-- 
Simon Riggs                http://www.EnterpriseDB.com/



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Slow standby snapshot
Next
From: Simon Riggs
Date:
Subject: Re: Pruning never visible changes