Re: Re[4]: Allowing WAL fsync to be done via O_SYNC

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Larry Rosenman <ler(at)lerctr(dot)org>
Cc: The Hermit Hacker <scrappy(at)hub(dot)org>, Alfred Perlstein <bright(at)wintelcom(dot)net>, Xu Yifeng <jamexu(at)telekbird(dot)com(dot)cn>, "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: Re[4]: Allowing WAL fsync to be done via O_SYNC
Date: 2001-03-16 17:36:12
Message-ID: 25302.984764172@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Larry Rosenman <ler(at)lerctr(dot)org> writes:
>> But, with shared libraries, are you really pulling in a "whole
>> thread-support library"?

> Yes, you are. On UnixWare, you need to add -Kthread, which CHANGES a LOT
> of primitives to go through threads wrappers and scheduling.

Right, it's not so much that we care about referencing another shlib,
it's that -lpthreads may cause you to get a whole new thread-aware
version of libc, with attendant overhead that we don't need or want.

regards, tom lane

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2001-03-16 17:50:41 Re: ["Stephen C. Tweedie" <sct@redhat.com>] Re: O_DSYNC flag for open
Previous Message Bruce Momjian 2001-03-16 17:34:27 Re: Re[4]: Allowing WAL fsync to be done via O_SYNC