Re: [PROPOSAL] Detecting plan changes with plan_id in pg_stat_activity

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Antonin Houska <ah(at)cybertec(dot)at>
Cc: "Imseih (AWS), Sami" <simseih(at)amazon(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PROPOSAL] Detecting plan changes with plan_id in pg_stat_activity
Date: 2022-07-14 07:13:10
Message-ID: 20220714071310.uien2tikv5ddr2vz@jrouhaud
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi,

On Thu, Jul 14, 2022 at 08:51:24AM +0200, Antonin Houska wrote:
> Shouldn't the patch status be set to "Waiting on Author"?
>
> (I was curious if this is a patch that I can review.)

Ah indeed, I just updated the CF entry!

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-07-14 08:00:08 Re: Backup command and functions can cause assertion failure and segmentation fault
Previous Message Antonin Houska 2022-07-14 06:51:24 Re: [PROPOSAL] Detecting plan changes with plan_id in pg_stat_activity