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

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Larry Rosenman <ler(at)lerctr(dot)org>
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:35:44
Message-ID: 200011171735.MAA26206@candle.pha.pa.us
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....

I would hope it just calls the function, and does not bring in thread
startup stuff.

--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026

In response to

Responses

Browse pgsql-hackers by date

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