Re: Is there any chance to get some kind of a result set sifting mechanism in Postgres?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: aa <ghevge(at)gmail(dot)com>
Cc: Wolfgang Wilhelm <wolfgang20121964(at)yahoo(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Is there any chance to get some kind of a result set sifting mechanism in Postgres?
Date: 2024-05-13 18:22:06
Message-ID: 828853.1715624526@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

aa <ghevge(at)gmail(dot)com> writes:
> If you call the action of "sifting" ordering, then yes. If you don't call
> it ordering, then no.
> In essence, is the output of a filtering mechanism, done in a single result
> set pass. And this pass should be the same pass in charge of collecting the
> result set in the first place.

Sounds a lot like a WHERE clause to me.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Noah Misch 2024-05-13 18:54:03 Re: race condition in pg_class
Previous Message Jacob Champion 2024-05-13 18:09:50 On the use of channel binding without server certificates (was: Direct SSL connection with ALPN and HBA rules)