| From: | "Steinar H(dot) Gunderson" <steinar+postgres(at)gunderson(dot)no> |
|---|---|
| To: | Greg Stark <stark(at)mit(dot)edu> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] Document heuristics for parameterized paths |
| Date: | 2021-12-16 16:04:40 |
| Message-ID: | 20211216160440.dyezkldzcrca5xva@sesse.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Dec 15, 2021 at 11:23:12PM -0500, Greg Stark wrote:
>>> +one that must cannot be delayed right away (because of outer join
>> must cannot?
> Actually on further reading... "delayed right away"?
There are two ways of writing this sentence, and I see that I tried to use
both of them in the same sentence :-) What about something like the
following?
This is enforced by refusing to join parameterized paths together unless
the parameterization is resolved, *or* the remaining parameterization is
one that cannot be resolved right away (because of outer join restrictions).
/* Steinar */
--
Homepage: https://www.sesse.net/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Larry Rosenman | 2021-12-16 16:11:59 | Re: Buildfarm support for older versions |
| Previous Message | Ronan Dunklau | 2021-12-16 16:03:39 | Re: Use generation context to speed up tuplesorts |