| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Antonin Houska <ah(at)cybertec(dot)at> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Define variable only in the scope that needs it |
| Date: | 2018-03-20 15:28:52 |
| Message-ID: | CA+TgmoYq0LvutaL5=Y9ZX6hLAQXoqObTpnLKpxe03CZLfbqdMg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Mar 20, 2018 at 7:11 AM, Antonin Houska <ah(at)cybertec(dot)at> wrote:
> I suppose the current definition in the higher scope is not intentional. This
> is what I suggest:
This is moot in light of commit 4f15e5d09de276fb77326be5567dd9796008ca2e.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michail Nikolaev | 2018-03-20 15:41:46 | Re: [WIP PATCH] Index scan offset optimisation using visibility map |
| Previous Message | Masahiko Sawada | 2018-03-20 15:28:44 | Re: XID-assigned idle transactions affect vacuum's job. |