Re: [PATCH] Optionally record Plan IDs to track plan changes for a query

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Sami Imseih <samimseih(at)gmail(dot)com>
Cc: Lukas Fittl <lukas(at)fittl(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Marko M <marko(at)pganalyze(dot)com>
Subject: Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Date: 2025-02-11 23:57:23
Message-ID: Z6vj4wnVe96dgGJx@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Feb 10, 2025 at 02:14:09PM -0600, Sami Imseih wrote:
> Another thought that I have is that If we mention that extensions can use
> these jumbling ( or whatever the final name is ) functions outside of
> core, it makes
> sense to actually show an example of this. What do you think?

Not sure. Do you have anything specific in mind that pgss is not able
to achieve with its jumbling based on the query strings?
--
Michael

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2025-02-11 23:58:42 Re: Enhance 'pg_createsubscriber' to retrieve databases automatically when no database is provided.
Previous Message Masahiko Sawada 2025-02-11 23:56:04 Re: pg_rewind with --write-recovery-conf option doesn't write dbname to primary_conninfo value.