| From: | Don Baccus <dhogaza(at)pacifier(dot)com> |
|---|---|
| To: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
| Cc: | Alfred Perlstein <bright(at)wintelcom(dot)net>, Vadim Mikheev <vmikheev(at)sectorbase(dot)com>, "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp>, peter_e(at)gmx(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: RE: [COMMITTERS] pgsql/src/backend/access/transam ( xact.c xlog.c) |
| Date: | 2000-11-16 19:36:34 |
| Message-ID: | 3.0.1.32.20001116113634.020feb80@mail.pacifier.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 02:13 PM 11/16/00 -0500, Bruce Momjian wrote:
>> I think the default should probably be no delay, and the documentation
>> on enabling this needs to be clear and obvious (i.e. hard to miss).
>
>I just talked to Tom Lane about this. I think a sleep(0) just before
>the flush would be the best. It would reliquish the cpu slice if
>another process is ready to run. If no other backend is running, it
>probably just returns. If there is another one, it gives it a chance to
>complete. On return from sleep(0), it can check if it still needs to
>flush. This would tend to bunch up flushers so they flush only once,
>while not delaying cases where only one backend is running.
This sounds like an interesting approach, yes.
- Don Baccus, Portland OR <dhogaza(at)pacifier(dot)com>
Nature photos, on-line guides, Pacific Northwest
Rare Bird Alert Service and other goodies at
http://donb.photo.net.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mitch Vincent | 2000-11-16 19:40:39 | Re: Varchar standard compliance |
| Previous Message | Max Fonin | 2000-11-16 19:24:20 | Enum type emulation: problem with opaque type in PL/pgSQL functions |