BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser

From: "Oleg" <serovov(at)gmail(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #5352: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Date: 2010-03-01 09:22:09
Message-ID: 201003010922.o219M9lk016559@wwwmaster.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs


The following bug has been logged online:

Bug reference: 5352
Logged by: Oleg
Email address: serovov(at)gmail(dot)com
PostgreSQL version: any
Operating system: any
Description: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Details:

CREATE TABLE test2 (
id BIGINT,
chunk_id BIGINT
);
CREATE TABLE test1 (
id BIGINT
);

CREATE OR REPLACE FUNCTION "bug" () RETURNS pg_catalog.void AS
$body$
DECLARE
row_test1 test1%rowtype;
row_test2 test2%rowtype;
BEGIN
SELECT test1, chunk_id
FROM test1 JOIN test2 ON(chunk.id = test2.chunk_id)
LIMIT 1
INTO row_test1, row_test2;

END;
$body$
LANGUAGE 'plpgsql' VOLATILE CALLED ON NULL INPUT SECURITY DEFINER;

Will throw error:
ERROR: LIMIT #,# syntax is not supported
HINT: Use separate LIMIT and OFFSET clauses.
QUERY: SELECT test1, chunk_id FROM test1 JOIN test2 ON(chunk.id =
test2.chunk_id) LIMIT 1, 0, $1
CONTEXT: SQL statement in PL/PgSQL function "bug" near line 8

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Oleg Serov 2010-03-01 09:22:33 Re: Bug in PL/PgSQL "SELECT .. INTO" statement parser
Previous Message Tom Lane 2010-03-01 02:39:28 Re: BUG #5351: compiling with --disable-shared is broken (patch included)