Re: Unportability of setvbuf() - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Unportability of setvbuf()
Date
Msg-id 20140515154801.GB9042@eldon.alvh.no-ip.org
Whole thread Raw
In response to Unportability of setvbuf()  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Unportability of setvbuf()
List pgsql-hackers
Tom Lane wrote:

> It might also be reasonable to create a wrapper macro along the line of
> "PG_STD_IO_BUFFERING()" that would encapsulate the whole sequence
>     setvbuf(stdout, NULL, _IOLBF, 0);
>     setvbuf(stderr, NULL, _IONBF, 0);
> Or maybe we should have separate macros for those two calls.  Or maybe
> this is just a useless layer of abstraction and PG_IOLBF is enough
> to make the calls portable.
> 
> Thoughts?

I don't really know all that much about this stuff, but see commits
6eda3e9c27781dec369542a9b20cba7c3d832a5e and its parent about
isolationtester.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Problem with txid_snapshot_in/out() functionality
Next
From: Bruce Momjian
Date:
Subject: Re: proposal: Set effective_cache_size to greater of .conf value, shared_buffers