| From: | Andrey Lepikhov <a(dot)lepikhov(at)postgrespro(dot)ru> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Hywel Carver <hywel(at)skillerwhale(dot)com>, pgsql-hackers(at)lists(dot)postgresql(dot)org |
| Cc: | Konstantin Knizhnik <knizhnik(at)garret(dot)ru> |
| Subject: | Re: Removing unneeded self joins |
| Date: | 2021-07-01 05:20:24 |
| Message-ID: | 1b4b177a-ef90-d3b9-59b2-5cec182f0efb@postgrespro.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30/6/21 18:55, Laurenz Albe wrote:
> On Wed, 2021-06-30 at 14:21 +0300, Andrey Lepikhov wrote:
>> I think, here we could ask more general question: do we want to remove a
>> 'IS NOT NULL' clause from the clause list if the rest of the list
>> implicitly implies it?
> Generally I have the impression that we are not too keen on spending
> planning time on optimizing cases that can be trivially improved by rewriting
> the query.
Thank you, It's strong argument.
Such feature would look better as a part of an enterprise edition.
--
regards,
Andrey Lepikhov
Postgres Professional
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-07-01 05:20:48 | Re: Preventing abort() and exit() calls in libpq |
| Previous Message | Noah Misch | 2021-07-01 04:53:09 | Re: Preventing abort() and exit() calls in libpq |