From: | kouber(at)saparev(dot)com |
---|---|
To: | pgsql-bugs(at)postgresql(dot)org |
Subject: | BUG #6483: Rows being evaluated, although being outside the LIMIT / OFFSET boundaries |
Date: | 2012-02-22 18:53:19 |
Message-ID: | E1S0HJX-0004pP-9Y@wrigleys.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
The following bug has been logged on the website:
Bug reference: 6483
Logged by: Kouber Saparev
Email address: kouber(at)saparev(dot)com
PostgreSQL version: 9.1.2
Operating system: Debian
Description:
The rows of a SELECT statement are being evaluated, even when not shown in
the final result, when using an OFFSET > 0. Although I know that LIMIT is
imposed just before flushing the result set to the client, this behaviour
seems quite confusing, especially when using DML statements in the field
list of the SELECT itself.
CREATE TABLE xxx (id INT);
CREATE FUNCTION f(xxx) RETURNS VOID AS $$
BEGIN
-- imagine some DML statements here --
RAISE NOTICE '%', $1.id;
END;
$$ LANGUAGE PLPGSQL;
INSERT INTO xxx VALUES (1), (2), (3), (4), (5);
-- shows a notice for 1 and 2
SELECT x.id, f(x) FROM xxx as x LIMIT 2;
-- shows a notice for 1, 2, 3 and 4
SELECT x.id, f(x) FROM xxx as x LIMIT 2 OFFSET 2;
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2012-02-22 18:58:43 | Re: BUG #6483: Rows being evaluated, although being outside the LIMIT / OFFSET boundaries |
Previous Message | Sergey Burladyan | 2012-02-22 18:37:31 | Re: BUG #6480: NLS text width problem |