Re: pg_stat_statements vs. SELECT FOR UPDATE

From: Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_stat_statements vs. SELECT FOR UPDATE
Date: 2019-01-20 01:11:19
Message-ID: a3039a19-f95f-2c75-f9da-4f3278874afa@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: pgsql-hackers

On 19/01/2019 18:02, Tom Lane wrote:
> Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)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 Content-Type Size
pgss.v002.patch text/x-patch 6.7 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-01-20 01:12:10 Re: [PROPOSAL] ON DELETE SET NULL (<column_list>) for Foreign Key Constraints
Previous Message Andrew Gierth 2019-01-20 00:41:32 Re: Changing SQL Inlining Behaviour (or...?)