| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | "Schmidt, Peter" <peter(dot)schmidt(at)prismedia(dot)com> |
| Cc: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "'Michael Ansley'" <Michael(dot)Ansley(at)intec-telecom-systems(dot)com>, "'pgsql-admin(at)postgresql(dot)org'" <pgsql-admin(at)postgresql(dot)org>, "Vadim B(dot) Mikheev" <vadim4o(at)email(dot)com> |
| Subject: | Re: v7.1b4 bad performance |
| Date: | 2001-02-17 03:43:17 |
| Message-ID: | 200102170343.WAA27926@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> The <varname>COMMIT_DELAY</varname> parameter defines for how long
> the backend will be forced to sleep after writing a commit record
> to the log with <function>LogInsert</function> call but before
> performing a <function>LogFlush</function>. This delay allows other
> backends to add their commit records to the log so as to have all
> of them flushed with a single log sync. Unfortunately, this
> mechanism is not fully implemented at release 7.1, so there is at
> present no point in changing this parameter from its default value
> of 5 microseconds.
Yes, I see Vadim mentioned the 5 microsecond default, and that was after
we already talked about it, so I guess he still wants the 5 to be there.
My idea was to see if another backend was near a commit, and only wait
in those cases. We certainly can't keep the code as it is for 7.1
final.
--
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Schmidt, Peter | 2001-02-17 03:54:45 | RE: v7.1b4 bad performance |
| Previous Message | Bruce Momjian | 2001-02-17 03:31:29 | Re: v7.1b4 bad performance |