Re: pread() and pwrite() - Mailing list pgsql-hackers

From Thomas Munro
Subject Re: pread() and pwrite()
Date
Msg-id CAEepm=1FDQOTtpSDP+VX15t1F+cg1jOHKNs-NNM=qFYYk_0++w@mail.gmail.com
Whole thread Raw
In response to Re: pread() and pwrite()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: pread() and pwrite()  (Tom Lane <tgl@sss.pgh.pa.us>)
Re: pread() and pwrite()  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Tue, Oct 9, 2018 at 2:55 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Thomas Munro <thomas.munro@enterprisedb.com> writes:
> > Rebased again.  Patches that touch AC_CHECK_FUNCS are fun like that!
>
> Yeah, I've been burnt by that too recently.  It occurs to me we could make
> that at least a little less painful if we formatted the macro with one
> line per function name:
>
> AC_CHECK_FUNCS([
>         cbrt
>         clock_gettime
>         fdatasync
>         ...
>         wcstombs_l
> ])
>
> You'd still get conflicts in configure itself, of course, but that
> doesn't require manual work to resolve -- just re-run autoconf.

+1, was about to suggest the same!

-- 
Thomas Munro
http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Function for listing archive_status directory
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] SERIALIZABLE with parallel query