Re: FETCH FIRST clause WITH TIES option

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Surafel Temesgen <surafel3000(at)gmail(dot)com>, Erik Rijkers <er(at)xs4all(dot)nl>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, David Steele <david(at)pgmasters(dot)net>, Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: FETCH FIRST clause WITH TIES option
Date: 2019-09-24 22:57:53
Message-ID: 9215.1569365873@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> writes:
> create table w (a point);

> # select * from w order by a fetch first 2 rows with ties;
> ERROR: could not identify an ordering operator for type point
> LINE 1: select * from w order by a fetch first 2 rows with ties;
> ^
> HINT: Use an explicit ordering operator or modify the query.

> I'm not sure that the HINT is useful here.

That's not new to this patch, HEAD does the same:

regression=# create table w (a point);
CREATE TABLE
regression=# select * from w order by a ;
ERROR: could not identify an ordering operator for type point
LINE 1: select * from w order by a ;
^
HINT: Use an explicit ordering operator or modify the query.

It is a meaningful hint IMO, since (in theory) you could add
something like "USING <<" to the ORDER BY to specify a
particular ordering operator. The fact that no suitable
operator is actually available in core doesn't seem like
a reason not to give the hint.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2019-09-24 23:07:02 Re: DROP SUBSCRIPTION with no slot
Previous Message Andres Freund 2019-09-24 22:57:16 Re: allocation limit for encoding conversion