Re: Define variables in the approprieate scope - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Define variables in the approprieate scope
Date
Msg-id 20200324005055.GC14565@momjian.us
Whole thread Raw
In response to Re: Define variables in the approprieate scope  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Define variables in the approprieate scope  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On Mon, Mar 23, 2020 at 01:00:24PM -0300, Alvaro Herrera wrote:
> On 2020-Mar-18, Bruce Momjian wrote:
> 
> > On Tue, Feb 25, 2020 at 09:35:52AM +0100, Antonin Houska wrote:
> > > I've noticed that two variables in RelationCopyStorage() are defined in a
> > > scope higher than necessary. Please see the patch.
> > 
> > It seems cleaner to me to allocate the variables once before the loop
> > starts, rather than for each loop iteration.
> 
> If we're talking about personal preference, my own is what Antonin
> shows.  However, since disagreement has been expressed, I think we
> should only change it if the generated code turns out better.

I am fine with either usage, frankly.  I was just pointing out what
might be the benefit of the current coding.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EnterpriseDB                             https://enterprisedb.com

+ As you are, so once was I.  As I am, so you will be. +
+                      Ancient Roman grave inscription +



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Autovacuum vs vac_update_datfrozenxid() vs ?
Next
From: Michael Paquier
Date:
Subject: Re: Define variables in the approprieate scope