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

From Bruce Momjian
Subject Re: Bug in PL/pgSQL GET DIAGNOSTICS?
Date
Msg-id 200209252221.g8PMLn903474@candle.pha.pa.us
Whole thread Raw
In response to Re: Bug in PL/pgSQL GET DIAGNOSTICS?  ("Michael Paesold" <mpaesold@gmx.at>)
Responses Re: Bug in PL/pgSQL GET DIAGNOSTICS?
List pgsql-hackers
Michael Paesold wrote:
> 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?

I already have a TODO item:
* Return proper effected tuple count from complex commands [return]

I am unsure if it will be fixed in 7.3 or not.  It is still on the open
items list, and I think we have a general plan to fix it.

--  Bruce Momjian                        |  http://candle.pha.pa.us pgman@candle.pha.pa.us               |  (610)
359-1001+  If your life is a hard drive,     |  13 Roberts Road +  Christ can be your backup.        |  Newtown Square,
Pennsylvania19073
 


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: compiling client utils under win32 - current 7.3devel is broken
Next
From: Tom Lane
Date:
Subject: Re: Bug in PL/pgSQL GET DIAGNOSTICS?