Re: PATCH: pgbench - option to build using ppoll() for larger connection counts

Rady, Doug <radydoug@amazon.com>

From: "Rady, Doug" <radydoug@amazon.com>
To: Fabien COELHO <coelho@cri.ensmp.fr>
Cc: Andres Freund <andres@anarazel.de>, "pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>, Robert Haas <robertmhaas@gmail.com>
Date: 2018-03-26T20:23:48Z
Lists: pgsql-hackers

Attachments

On 3/25/18, 04:00, "Fabien COELHO" <coelho@cri.ensmp.fr> wrote:

Hello Fabien,
    
    Hello Doug,
    
    > Updated the patch to not do the #undef
    > pgbench11-ppoll-v11.patch attached.
    
    Patch applies. Do not forget to regenerate configure to test...
    
    I've compiled and run with both ppoll & select options without issues.
    
    Two quite minor style comment (at least 2 instances):
    
       if (cond) return false; else return true;
    
    ISTM that the simpler the better:
    
       return !cond;
 Fixed.
   
    Also ISTM that the following does not comply with pg C style expectations 
    (idem, 2 instances):
    
       } else {
 Fixed.

Also fixed issue with 'timeout' not being passed as NULL when no timeout time.
    
    -- 
    Fabien.

Thanks!
doug



    
    

Commits

  1. Use ppoll(2), if available, to wait for input in pgbench.

  2. Use pselect(2) not select(2), if available, to wait in postmaster's loop.