From: Dimitrios Apostolou <jimis@gmx.net>
To: David Rowley <dgrowleyml@gmail.com>
Cc: pgsql-general@lists.postgresql.org
Subject: Re: Inefficient query plan for SELECT ... EXCEPT ...
Date: Wed, 1 Nov 2023 14:32:51 +0100 (CET)
Message-ID: <b0e381b1-2352-d8eb-3e56-3eda8a422130@gmx.net> (raw)
In-Reply-To: <CAApHDvogxAy+RFSQ+-h7BO-Bu0LoHf0kmV7cPdb9WypRserv8g@mail.gmail.com>
References: <86c352b6-c0ec-8c4d-9506-297506b1b5da@gmx.net>
<CAApHDvogxAy+RFSQ+-h7BO-Bu0LoHf0kmV7cPdb9WypRserv8g@mail.gmail.com>
Thank you all for the answers, they covered me well.
>> Is this worth a bug report? I can file one if the issue is not known.
>
> No. It's just a missing optimisation. We know about it.
It's good I shot an email first then. FWIW my usual way in other projects
would be to check the bugtracker, and just "follow" the relevant issue if
it's minor like a missing optimisation. I didn't find a way to search for
"known issues" in the Postgresql project.
Dimitris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: jimis@gmx.net, dgrowleyml@gmail.com
Subject: Re: Inefficient query plan for SELECT ... EXCEPT ...
In-Reply-To: <b0e381b1-2352-d8eb-3e56-3eda8a422130@gmx.net>
References: <86c352b6-c0ec-8c4d-9506-297506b1b5da@gmx.net> <CAApHDvogxAy+RFSQ+-h7BO-Bu0LoHf0kmV7cPdb9WypRserv8g@mail.gmail.com> <b0e381b1-2352-d8eb-3e56-3eda8a422130@gmx.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox