| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Joel Jacobson <joel(at)trustly(dot)com> |
| Subject: | Re: merging some features from plpgsql2 project |
| Date: | 2017-01-07 11:39:39 |
| Message-ID: | CAFj8pRBErF0ysXMXPmQ58f5Uowed8bjSx+iWBW6bc+jiROYFeg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2017-01-07 12:32:53 | Re: Make pg_basebackup -x stream the default |
| Previous Message | Magnus Hagander | 2017-01-07 11:23:35 | Re: Replication/backup defaults |