Re: Shave a few instructions from child-process startup sequence - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: Shave a few instructions from child-process startup sequence
Date
Msg-id 528CD37A.4020206@gmx.net
Whole thread Raw
In response to Re: Shave a few instructions from child-process startup sequence  (Gurjeet Singh <gurjeet@singh.im>)
Responses Re: Shave a few instructions from child-process startup sequence  (Gurjeet Singh <gurjeet@singh.im>)
List pgsql-hackers
On 11/5/13, 2:47 AM, Gurjeet Singh wrote:
> On Mon, Nov 4, 2013 at 12:20 AM, Tom Lane <tgl@sss.pgh.pa.us
> <mailto:tgl@sss.pgh.pa.us>> wrote:
> 
>     But we're not buying much.  A few instructions during postmaster
>     shutdown
>     is entirely negligible.
> 
> 
> The patch is for ClosePostmasterPorts(), which is called from every
> child process startup sequence (as $subject also implies), not in
> postmaster shutdown. I hope that adds some weight to the argument.

If there is a concern about future maintenance, you could add assertions
(in appropriate compile mode) that the rest of the array is indeed
PGINVALID_SOCKET.  I think that could be a win for both performance and
maintainability.



pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Suggestion: Issue warning when calling SET TRANSACTION outside transaction block
Next
From: Magnus Hagander
Date:
Subject: Re: Autoconf 2.69 update