Re: Proposal: QUALIFY clause

From: Vik Fearing <vik(at)postgresfriends(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Isaac Morland <isaac(dot)morland(at)gmail(dot)com>
Cc: Mike Artz <michaeleartz(at)gmail(dot)com>, Matheus Alcantara <matheusssilv97(at)gmail(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>, Peter Eisentraut <peter(at)eisentraut(dot)org>
Subject: Re: Proposal: QUALIFY clause
Date: 2025-07-21 20:20:16
Message-ID: 88d8f6c9-d19d-4cee-bbc5-826987c14587@postgresfriends.org
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 21/07/2025 16:41, Tom Lane wrote:
> Isaac Morland <isaac(dot)morland(at)gmail(dot)com> writes:
>> I'll be honest, I'm skeptical that we need another keyword that basically
>> means “WHERE, but applied at a different point in the query processing”.
> That was my reaction too. I'm especially skeptical that getting out
> front of the SQL standards committee is a good thing to do. If and
> when this shows up in the standard, then sure.

It's "when", not "if".  I submitted a paper for this to the committee
two years ago, but it was just a discussion paper and not an actual
change proposal.  I have recently revived that paper so hopefully it
will be accepted within the next year.  I would even like to push so
that we have it in 19.

--

Vik Fearing

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2025-07-21 20:20:55 Re: Verify predefined LWLocks tranches have entries in wait_event_names.txt
Previous Message Masahiko Sawada 2025-07-21 19:41:49 Re: Parallel heap vacuum