Re: plpgsql on 8.0b4 bug?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: James Robinson <jlrobins(at)socialserve(dot)com>
Cc: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: plpgsql on 8.0b4 bug?
Date: 2004-11-18 16:14:41
Message-ID: 17200.1100794481@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

James Robinson <jlrobins(at)socialserve(dot)com> writes:
> 7.4.6 results:
> xs2 /tmp> psql ssc_sav < pets.sql
> BEGIN
> ALTER TABLE
> CREATE FUNCTION
> ERROR: syntax error at or near "ELSEIF" at character 1
> CONTEXT: PL/pgSQL function "fix_pets" line 16 at SQL statement

Um ... I get the "no code determined" message in 7.4.6 too, and indeed
in every version of plpgsql (ok, I didn't try before 7.2). Given the
way plpgsql works, it'd be hard to make it do anything else. It thinks
that ELSEIF (or any other unrecognized keyword) is a SQL command keyword.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message James Robinson 2004-11-18 16:28:13 Re: plpgsql on 8.0b4 bug?
Previous Message David Parker 2004-11-18 16:12:12 Re: query plan question