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

From Vik Fearing
Subject Re: pg_stat_statements vs. SELECT FOR UPDATE
Date
Msg-id a3039a19-f95f-2c75-f9da-4f3278874afa@2ndquadrant.com
Whole thread Raw
In response to Re: pg_stat_statements vs. SELECT FOR UPDATE  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pg_stat_statements vs. SELECT FOR UPDATE  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
On 19/01/2019 18:02, Tom Lane wrote:
> Vik Fearing <vik.fearing@2ndquadrant.com> writes:
>> Does the extension need a version bump for this?
> 
> We don't bump its version when we make any other change that affects
> its hash calculation.  I don't think this could be back-patched,
> but Andrew wasn't proposing to do so (IIUC).

OK perfect.

Here is Andrew's original patch, but with some tests.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support

Attachment

pgsql-hackers by date:

Previous
From: Andrew Gierth
Date:
Subject: Re: Changing SQL Inlining Behaviour (or...?)
Next
From: Tom Lane
Date:
Subject: Re: [PROPOSAL] ON DELETE SET NULL () for Foreign Key Constraints