| From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Vadim Mikheev <vadim4o(at)email(dot)com> |
| Cc: | pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: CommitDelay performance improvement |
| Date: | 2001-02-24 03:59:42 |
| Message-ID: | 3.0.5.32.20010224145942.03246e80@mail.rhyme.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
At 11:32 23/02/01 -0500, Tom Lane wrote:
>Looking at the XLOG stuff, I notice that we already have a field
>(logRec) in the per-backend PROC structures that shows whether a
>transaction is currently in progress with at least one change made
>(ie at least one XLOG entry written).
Would it be worth adding a field 'waiting for fsync since xxx', so the
second process can (a) log that it is expecting someone else to FSYNC (for
perf stats, if we want them), and (b) wait for (xxx + delta)ms/us etc?
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.B.N. 75 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-02-24 04:03:40 | Re: CommitDelay performance improvement |
| Previous Message | Philip Warner | 2001-02-24 03:56:42 | Re: CommitDelay performance improvement |