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

From Laurenz Albe
Subject Re: Pruning never visible changes
Date
Msg-id 179f7c0c556731d66159669a69a3e5f6e3fa8d04.camel@cybertec.at
Whole thread Raw
In response to Re: Pruning never visible changes  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Pruning never visible changes
List pgsql-hackers
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

Yours,
Laurenz Albe



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Fix gin index cost estimation
Next
From: Tom Lane
Date:
Subject: Re: clang 15 doesn't like our JIT code