Re: [HACKERS] merging some features from plpgsql2 project - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: [HACKERS] merging some features from plpgsql2 project
Date
Msg-id CAFj8pRAODqxPL_U36u9R33u4y16VVeT2=RY-cKyHFnWDSJeZCg@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] merging some features from plpgsql2 project  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] merging some features from plpgsql2 project  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers


2017-01-10 5:59 GMT+01:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
On 1/7/17 6:39 AM, Pavel Stehule wrote:
> ROW_COUNT .. shortcut for GET DIAGNOSTICS row_count = ROW_COUNT.

I don't see the point.

A check how much rows was impacted by query is relative often task. So we can do this task more user friendly.

Second motivation - ROW_COUNT is working for static and for dynamic SQL - it can be partial replace of FOUND variable.

But now, when I am thinking about it - it can be strange for some users too. Pretty often we use implicit LIMIT for query execution. So ROW_COUNT can be probably different than users expecting.

Regards

Pavel
 

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] merging some features from plpgsql2 project
Next
From: Alvaro Herrera
Date:
Subject: [HACKERS] remove floats from bootstrap scanner/parser