On Tue, Feb 21, 2023 at 9:46 AM Peter Geoghegan wrote:
> All that you need is two statements within the same READ COMMITTED
> transaction, combined with a second concurrently executing
> transaction. The second transaction need only start after the first
> one (giving it a later XID), and then com
On Tue, Feb 21, 2023 at 1:51 AM Laurenz Albe wrote:
> > If the current transaction isolation level is read committed it absolutely
> > can see rows committed by future transactions with higher XIDs.
>
> You are right, in combination with PlanQualEval you can.
You don't need to bring EvalPlanQual
On Sun, 2023-02-19 at 03:10 +, PG Doc comments form wrote:
> The following documentation comment has been logged on the website:
>
> Page: https://www.postgresql.org/docs/15/routine-vacuuming.html
> Description:
>
> hey guys
>
> thanks for the work you do we really appreciate it.
>
> In th
