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

From: Sami Imseih <samimseih(at)gmail(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
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-10 20:14:09
Message-ID: CAA5RZ0vSEq-kUJsw_mkbn7JCU_XefPEkTY=EEyKerQ9JT0hGMQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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?

--
Sami

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Matheus Alcantara 2025-02-10 20:43:22 Re: explain analyze rows=%.0f
Previous Message Sami Imseih 2025-02-10 20:02:10 Re: [PATCH] Optionally record Plan IDs to track plan changes for a query