| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, "Jonathan S(dot) Katz" <jkatz(at)postgresql(dot)org>, Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Geoghegan <pg(at)bowt(dot)ie>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com> |
| Subject: | Re: Improving connection scalability: GetSnapshotData() |
| Date: | 2020-04-08 22:25:34 |
| Message-ID: | 20200408222534.56ys4lt7xd3dvgqu@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2020-04-08 18:06:23 -0400, Bruce Momjian wrote:
> If we don't commit this, where does this leave us with the
> old_snapshot_threshold feature? We remove it in back branches and have
> no working version in PG 13? That seems kind of bad.
I don't think this patch changes the situation for
old_snapshot_threshold in a meaningful way.
Sure, this patch makes old_snapshot_threshold scale better, and triggers
fewer unnecessary query cancellations. But there still are wrong query
results, the tests still don't test anything meaningful, and the
determination of which query is cancelled is still wrong.
- Andres
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2020-04-08 22:51:11 | Perl modules for testing/viewing/corrupting/repairing your heap files |
| Previous Message | Ants Aasma | 2020-04-08 22:24:59 | Re: Parallel copy |