Prev: Replication documentation addition
Next: New feature request: FlashBack Query
From: Bruce Momjian on 26 Jan 2007 21:28
Tom Lane wrote:
> Heikki Linnakangas <heikki(a)enterprisedb.com> writes:
> > I'd like to see still more evidence that it's a problem before we start
> > changing that piece of code. It has served us well for years.
>
> What I see here is mostly evidence suggesting that we should consider
> raising NUM_CLOG_BUFFERS, rather than anything more invasive.

Added to TODO:

* Consider increasing NUM_CLOG_BUFFERS

--
Bruce Momjian bruce(a)momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster

From: Bruce Momjian on 26 Jan 2007 21:29
Pavan Deolasee wrote:
> On 1/26/07, Tom Lane <tgl(a)sss.pgh.pa.us> wrote:
> >
> >
> > I think what he's suggesting is deliberately not updating the hint bits
> > during a SELECT ...
>
>
> No, I was suggesting doing it in bgwriter so that we may not need to that
> during
> a SELECT. Of course, we need to investigate more and have numbers to prove
> the need. Also you have already expressed concerns that doing so in bgwriter
> is deadlock
> prone. So there is certainly more work needed for any such scheme to work.

Added to TODO:

* Consider having the background writer update the transaction status
hint bits before writing out the page

--
Bruce Momjian bruce(a)momjian.us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate

First  |  Prev  | 
Pages: 1 2 3 4 5 6
Prev: Replication documentation addition
Next: New feature request: FlashBack Query