| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | reg_pg_stefanz(at)perfexpert(dot)ch |
| Cc: | "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: ERROR: no known snapshots |
| Date: | 2021-05-12 03:42:03 |
| Message-ID: | 1033239.1620790923@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
reg_pg_stefanz(at)perfexpert(dot)ch writes:
> it run into an issue with: ERROR: no known snapshots
Hi! This has been reported before, but I'm embarrassed to say that
the previous report seems to have fallen between the cracks.
I've created a patch [1] that resolves your example as presented.
If you're in a position to apply the patch and see if it resolves
your real non-simplified case, that would be very helpful.
Also, this fix in principle will create a small performance
penalty for FOR-loops in non-atomic contexts such as DO loops.
It'd be interesting to know if the penalty is noticeable in
your usage.
regards, tom lane
[1] https://www.postgresql.org/message-id/1032535.1620789957%40sss.pgh.pa.us
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Vijaykumar Jain | 2021-05-12 05:19:53 | Re: force partition pruning |
| Previous Message | Niels Jespersen | 2021-05-12 02:46:30 | SV: force partition pruning |