Any reason not to return row_count in cursor of plpgsql?

From: laser <laserlist(at)pgsqldb(dot)com>
To: Postgres - Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Any reason not to return row_count in cursor of plpgsql?
Date: 2008-07-21 01:39:54
Message-ID: 4883E8EA.6020702@pgsqldb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

hi all,

I read the code that it seems easy for the cursor in plpgsql to return
ROW_COUNT after
MOVE LAST etc. The SPI_processed variable already there, but didn't put
it into estate
structure, any reason for that?

thanks and best regards

-laser

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message daveg 2008-07-21 01:49:42 Re: pg_dump additional options for performance
Previous Message Stephen Frost 2008-07-21 01:18:29 Re: pg_dump additional options for performance