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 CAFj8pRBErF0ysXMXPmQ58f5Uowed8bjSx+iWBW6bc+jiROYFeg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] merging some features from plpgsql2 project  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: [HACKERS] merging some features from plpgsql2 project  (Jim Nasby <Jim.Nasby@BlueTreble.com>)
Re: [HACKERS] merging some features from plpgsql2 project  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers



* EXECUTE and FOUND - this is incompatible change, extra check can be used (test on unset variable). I see solution in leaving FOUND variable and introduction of some new without this issue - ROW_COUNT maybe (this is another possible incompatible change, but with higher benefit - maybe we can introduce some aliasing, PRAGMA clause, default PRAGMAs, ..).

I checked current implementation of FOUND variable. If we introduce new auto variable ROW_COUNT - exactly like FOUND, then it doesn't introduce any compatibility break. 

ROW_COUNT .. shortcut for GET DIAGNOSTICS row_count = ROW_COUNT. 

Comments, notes?

Regards

Pavel


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: [HACKERS] Replication/backup defaults
Next
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Make pg_basebackup -x stream the default