Re: Is there a way to identify a plan generated by GECO?

2025-07-17 Thread Tom Lane
Jerry Brenner writes: > I don't have any background with the randomized search. Does the repeated > pattern with the same plan being executed multiple times in a time range > and then the plan changes, never to change back, match the expectation with > the randomization? [ shrug... ] Insufficie

Re: Is there a way to identify a plan generated by GECO?

2025-07-17 Thread Jerry Brenner
Thanks for the quick response! I don't have any background with the randomized search. Does the repeated pattern with the same plan being executed multiple times in a time range and then the plan changes, never to change back, match the expectation with the randomization? Thanks, Jerry On Thu, J

Re: Is there a way to identify a plan generated by GECO?

2025-07-17 Thread Tom Lane
Jerry Brenner writes: > We are on Postgres 15.5 (Aurora) and capturing query plans via > auto_explain. We are seeing a large number of query plans for 2 queries > that have 12 tables. Every fast (or "fast enough") plan has a left deep > tree and every slow plan has a bushy tree. Is there a way

Re: Is there a way to identify a plan generated by GECO?

2025-07-17 Thread Nikolay Samokhvalov
On Thu, Jul 17, 2025 at 18:11 Jerry Brenner wrote: > We are on Postgres 15.5 (Aurora) and capturing query plans via > auto_explain. We are seeing a large number of query plans for 2 queries > that have 12 tables. Every fast (or "fast enough") plan has a left deep > tree and every slow plan has

Is there a way to identify a plan generated by GECO?

2025-07-17 Thread Jerry Brenner
We are on Postgres 15.5 (Aurora) and capturing query plans via auto_explain. We are seeing a large number of query plans for 2 queries that have 12 tables. Every fast (or "fast enough") plan has a left deep tree and every slow plan has a bushy tree. Is there a way to determine if a plan was gen