From: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
---|---|
To: | Japin Li <japinli(at)hotmail(dot)com> |
Cc: | Etsuro Fujita <etsuro(dot)fujita(at)gmail(dot)com>, onderkalaci(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org |
Subject: | Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption |
Date: | 2024-05-16 15:27:18 |
Message-ID: | 202405161527.2rs7jfxkxl6m@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On 2024-May-16, Japin Li wrote:
> I find that the FETCH FIRST ... ROWS WITH TIES does not support type casting.
> For example:
>
> postgres=# SELECT * FROM pg_class ORDER BY relname FETCH FIRST 2::bigint ROWS WITH TIES;
> ERROR: syntax error at or near "::"
> LINE 1: ...ECT * FROM pg_class ORDER BY relname FETCH FIRST 2::bigint R...
> ^
Why do you need this? The standard says
<fetch first clause> ::= FETCH { FIRST | NEXT } [ <fetch first quantity> ] { ROW | ROWS } { ONLY | WITH TIES }
<fetch first quantity> ::= <fetch first row count> | <fetch first percentage>
<offset row count> ::= <simple value specification>
<fetch first row count> ::= <simple value specification>
which doesn't seem to leave room for a cast.
I didn't try super extensively, but this works:
select 1 from pg_class fetch first 281474976710656 rows only;
so the count is already not restricted to be an int32 value.
--
Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Japin Li | 2024-05-16 16:15:33 | Re: BUG #18467: postgres_fdw (deparser) ignores LimitOption |
Previous Message | David G. Johnston | 2024-05-16 14:39:43 | Re: differences between <> and != when using signed values on the right hand side |