| From: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Pruning never visible changes |
| Date: | 2022-09-16 20:07:48 |
| Message-ID: | 179f7c0c556731d66159669a69a3e5f6e3fa8d04.camel@cybertec.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | Postg토토 핫SQL : |
On Fri, 2022-09-16 at 10:26 -0400, Tom Lane wrote:
> Simon Riggs <simon(dot)riggs(at)enterprisedb(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2022-09-16 20:07:51 | Re: clang 15 doesn't like our JIT code |
| Previous Message | Tom Lane | 2022-09-16 20:04:59 | Re: Fix gin index cost estimation |