Re: [PATCH] Optionally record Plan IDs to track plan changes for a query - Mailing list pgsql-hackers

From Sami Imseih
Subject Re: [PATCH] Optionally record Plan IDs to track plan changes for a query
Date
Msg-id CAA5RZ0vnAdfJjAQQjxYLjS-zrkXBjwRrT=+uSFP7YPtWioErig@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] Optionally record Plan IDs to track plan changes for a query  (Alvaro Herrera <alvherre@alvh.no-ip.org>)
List pgsql-hackers
> I don't understand why we would change any naming here at all.  I think
> you should be looking at a much broader consensus and plus-ones that a
> renaming is needed.  -1 from me.

The reason for the change is because "query jumble" will no longer
make sense if the jumble code can now be used for other types of
trees, such as Plan.

I do agree that this needs a single-threaded discussion to achieve a
consensus.

--

Sami



pgsql-hackers by date:

Previous
From: Pavel Borisov
Date:
Subject: Re: Get rid of WALBufMappingLock
Next
From: Justin Pryzby
Date:
Subject: pg17.3 PQescapeIdentifier() ignores len