Re: Cleanup - adjust the code crossing 80-column window limit - Mailing list pgsql-hackers

From Amul Sul
Subject Re: Cleanup - adjust the code crossing 80-column window limit
Date
Msg-id CAAJ_b97DsWbacuFkbqTaY0iFo7L2NSDn6h-ttiBUs4sQqC-UkA@mail.gmail.com
Whole thread Raw
In response to Re: Cleanup - adjust the code crossing 80-column window limit  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
Responses Re: Cleanup - adjust the code crossing 80-column window limit  (Bharath Rupireddy <bharath.rupireddyforpostgres@gmail.com>)
List pgsql-hackers
On Wed, Jul 1, 2020 at 4:29 PM Bharath Rupireddy
<bharath.rupireddyforpostgres@gmail.com> wrote:
>
> changes look good to me.

Thanks for looking at the patch.

>
> one comment: instead of having block variables onexit, in the while
> loops in shmem_exit, can we have a single local variable defined at
> the start of the shmem_exit function
> and reuse them in the while loops? same comment for onexit block
> variable in proc_exit_prepare() function.
>

If you are worried about the declaration and initialization of the variable will
happen with every loop cycle then you shouldn't because that happens only
once before the loop-block is entered.

Regards,
Amul



pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: max_slot_wal_keep_size and wal_keep_segments
Next
From: "Drouvot, Bertrand"
Date:
Subject: Re: Add Information during standby recovery conflicts