| From: | David Rowley <dgrowleyml(at)gmail(dot)com> |
|---|---|
| To: | Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Alexander Alexander <alexander(dot)berezin3000(at)gmail(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n |
| Date: | 2024-06-06 08:27:50 |
| Message-ID: | CAApHDvoQmbesAm93i6mC_kzi_6x3ng-XT2Na9OFfSnw=eGisag@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Thu, 6 Jun 2024 at 20:10, Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at> wrote:
>
> On Thu, 2024-06-06 at 17:04 +1200, David Rowley wrote:
> > If the user has some genuine reason for creating a NULLS FIRST index
> > for some other query, then it might be nice if we were able to use
> > that index for Merge Joins instead of them having to create another
> > index to speed up the join query.
>
> I cannot imagine a genuine reason for creating a NULLS FIRST index
> on a NOT NULL column, but perhaps I am too narrow-minded.
You didn't quote the part where I said "if you had two nullable
columns". It might be worth rereading what I wrote and taking the time
to understand it.
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Bug reporting form | 2024-06-06 09:36:15 | BUG #18497: Heap-use-after-free in plpgsql |
| Previous Message | Laurenz Albe | 2024-06-06 08:10:53 | Re: BUG #18477: A specific SQL query with "ORDER BY ... NULLS FIRST" is performing poorly if an ordering column is n |