Re: Bug in PL/pgSQL GET DIAGNOSTICS? - Mailing list pgsql-hackers

From Michael Paesold
Subject Re: Bug in PL/pgSQL GET DIAGNOSTICS?
Date
Msg-id 031e01c264d9$d28a3930$4201a8c0@beeblebrox
Whole thread Raw
In response to Re: PGXLOG variable worthwhile?  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Bug in PL/pgSQL GET DIAGNOSTICS?  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tom Lane wrote:

> "Michael Paesold" <mpaesold@gmx.at> writes:
> > I have come across a problem (bug?) with PL/pgSQL GET DIAGNOSTICS.
>
> Hm.  This seems to be SPI's version of the same definitional issue
> we're contending with for status data returned from an interactive
> query: SPI is currently set up to return the status of the last
> querytree it executes, which is probably the wrong thing to do in the
> presence of rule rewrites.  But I'm hesitant to change SPI until we know
> what we're going to do for interactive query status.
>
> regards, tom lane

So this is not going to be fixed for 7.3 I suggest, no? Can you add the
issue to the TODO list or can this thread be added to any appropriate TODO
item?

Regards,
Michael Paesold



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Bug in PL/pgSQL GET DIAGNOSTICS?
Next
From: "Michael Paesold"
Date:
Subject: Re: Insert Performance