Re: Segfault on ANALYZE in SERIALIZABLE isolation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Sergei Kornilov <sk(at)zsrv(dot)org>, Joe Wildish <joe-postgresql(dot)org(at)elusive(dot)cx>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Segfault on ANALYZE in SERIALIZABLE isolation
Date: 2019-05-18 19:48:47
Message-ID: 698.1558208927@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Andres Freund <andres(at)anarazel(dot)de> writes:
> Not quite - that was about the DML callbacks, this is about the scan itself. And while we have a snapshot allocated, the analyze version of the beginscan intentionally doesn't take a snapshot.

Uh, what? That's a *huge* regression. See, eg, 7170268ef. We
really want ANALYZE to act as though it's reading a normal MVCC
snapshot.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2019-05-18 20:12:41 Re: Segfault on ANALYZE in SERIALIZABLE isolation
Previous Message Tom Lane 2019-05-18 19:45:11 Re: Multivariate MCV stats can leak data to unprivileged users