Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c)
| От | Larry Rosenman |
|---|---|
| Тема | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
| Дата | |
| Msg-id | 20001117114201.A12289@lerami.lerctr.org обсуждение исходный текст |
| Ответ на | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) (Bruce Momjian <pgman@candle.pha.pa.us>) |
| Список | pgsql-hackers |
* Bruce Momjian <pgman@candle.pha.pa.us> [001117 11:39]: > > * Bruce Momjian <pgman@candle.pha.pa.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. I suspect it DOES bring in the thread startup and all that implies... Tread lightly. The good news is UnixWare Threads are LWP's and the kernel is multithreaded... LER > > -- > Bruce Momjian | http://candle.pha.pa.us > pgman@candle.pha.pa.us | (610) 853-3000 > + If your life is a hard drive, | 830 Blythe Avenue > + Christ can be your backup. | Drexel Hill, Pennsylvania 19026 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 972-414-9812 (voice) Internet: ler@lerctr.org US Mail: 1905 Steamboat Springs Drive, Garland, TX 75044-6749
В списке pgsql-hackers по дате отправления: