Re: Bug#98643: plpgsql SELECT INTO causes trouble when assignment impossible (fwd)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Oliver Elphick" <olly(at)lfix(dot)co(dot)uk>
Cc: pgsql-hackers(at)postgresql(dot)org, Michal Politowski <mpol(at)charybda(dot)icm(dot)edu(dot)pl>
Subject: Re: Bug#98643: plpgsql SELECT INTO causes trouble when assignment impossible (fwd)
Date: 2001-05-25 14:23:01
Message-ID: 5024.990800581@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

"Oliver Elphick" <olly(at)lfix(dot)co(dot)uk> writes:
> psql:x.sql:13: pqReadData() -- backend closed the channel unexpectedly.

This is the already-fixed-in-7.1.2 problem with empty SELECTs in
plpgsql.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-05-25 14:26:11 Re: PQsetdbLogin bug?
Previous Message Tom Lane 2001-05-25 13:47:26 Re: GiST index on data types that require compression