Re: Make EXPLAIN generate a generic plan for a parameterized query
От | Andres Freund |
---|---|
Тема | Re: Make EXPLAIN generate a generic plan for a parameterized query |
Дата | |
Msg-id | 20221206181708.ict3to72wynzo3ao@awork3.anarazel.de обсуждение исходный текст |
Ответ на | Re: Make EXPLAIN generate a generic plan for a parameterized query (Laurenz Albe <laurenz.albe@cybertec.at>) |
Ответы |
Re: Make EXPLAIN generate a generic plan for a parameterized query
|
Список | pgsql-hackers |
Hi, On 2022-10-29 10:35:26 +0200, Laurenz Albe wrote: > On Tue, 2022-10-25 at 19:03 +0800, Julien Rouhaud wrote: > > On Tue, Oct 25, 2022 at 11:08:27AM +0200, Laurenz Albe wrote: > > > Here is a patch that > > > implements it with an EXPLAIN option named GENERIC_PLAN. > > > > I only have a quick look at the patch for now. Any reason why you don't rely > > on the existing explain_filter() function for emitting stable output (without > > having to remove the costs)? It would also take care of checking that it works > > in plpgsql. > > No, there is no principled reason I did it like that. Version 2 does it like > you suggest. This fails to build the docs: https://cirrus-ci.com/task/5609301511766016 [17:47:01.064] ref/explain.sgml:179: parser error : Opening and ending tag mismatch: likeral line 179 and literal [17:47:01.064] <likeral>ANALYZE</literal>, since a statement with unknown parameters [17:47:01.064] ^ Greetings, Andres Freund
В списке pgsql-hackers по дате отправления: