Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)

From: Larry Rosenman <ler(at)lerctr(dot)org>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: Tom Samplonius <tom(at)sdf(dot)com>, Alfred Perlstein <bright(at)wintelcom(dot)net>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
Date: 2000-11-17 17:26:22
Message-ID: 20001117112622.A11351@lerami.lerctr.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

* Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> [001117 11:23]:
> > > sleep(3) should conform to POSIX specification, if anyone has the
> > > reference they can check it to see what the effect of sleep(0)
> > > should be.
> >
> > Yes, but Posix also specifies sched_yield() which rather explicitly
> > allows a process to yield its timeslice. No idea how well that is
> > supported.
>
> I have it on BSDI. We could add a configure check, and use it if it is
> there. Another idea is to add a shared memory flag when someone enters
> the 'commit' section of the transaction code. That way, a backend could
> check to see if another process is _about_ to commit, and wait.
On UnixWare, it requires the -Kthread or -Kpthread command, which then
links in the threads library...

I'm not sure that this is a good thing or not....

LER

--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 972-414-9812 (voice) Internet: ler(at)lerctr(dot)org
US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-11-17 17:34:27 Re: Coping with 'C' vs 'newC' function language names
Previous Message Bruce Momjian 2000-11-17 17:16:06 Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)