Re: pg_stat_statements vs. SELECT FOR UPDATE - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: pg_stat_statements vs. SELECT FOR UPDATE
Date
Msg-id CA+hUKGLuKz0oFaHSqCThXHMw1ZpUi7F=5q2zZv+Y0NAcgxreDg@mail.gmail.com
Whole thread Raw
In response to Re: pg_stat_statements vs. SELECT FOR UPDATE  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
On Thu, Jul 11, 2019 at 9:08 PM Sergei Kornilov <sk@zsrv.org> wrote:
> Patch is still applied cleanly on HEAD and passes check-world. I think ignoring FOR UPDATE clause is incorrect
behavior.

With my reviewer hat: I agree.

With my CFM hat: It seems like this patch is ready to land so I have
set it to "Ready for Committer".  But don't worry if you were hoping
to review this and missed out, we have two more pg_stat_statements
patches that need your feedback!

https://commitfest.postgresql.org/23/2080/
https://commitfest.postgresql.org/23/1999/

-- 
Thomas Munro
https://enterprisedb.com



pgsql-hackers by date:

Previous
From: Shawn Debnath
Date:
Subject: Re: Introduce timeout capability for ConditionVariableSleep
Next
From: Thomas Munro
Date:
Subject: Re: Why is infinite_recurse test suddenly failing?