Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: PostgreSQL Caching
- From: Brad Nicholson <bnichols(at)ca(dot)afilias(dot)info>
- To: "Tomeh, Husam" <htomeh(at)firstam(dot)com>
- Cc: Adnan DURSUN <a_dursun(at)hotmail(dot)com>, pgsql-performance(at)postgresql(dot)org
- Subject: Re: PostgreSQL Caching
- Date: Wed, 04 Oct 2006 09:52:26 -0400
- Message-id: <1159969946(dot)15773(dot)23(dot)camel(at)dba5(dot)int(dot)libertyrms(dot)com>
On Tue, 2006-10-03 at 18:29 -0700, Tomeh, Husam wrote: > >> * When any session updates the data that already in shared > buffer, > >>does Postgres synchronize the data both disk and shared buffers area > >> immediately ? > > Not necessarily true. When a block is modified in the shared buffers, > the modified block is written to the Postgres WAL log. A periodic DB > checkpoint is performed to flush the modified blocks in the shared > buffers to the data files. Postgres 8.0 and beyond have a process called bgwriter that continually flushes dirty buffers to disk, to minimize the work that needs to be done at checkpoint time.
- References:
- Re: PostgreSQL Caching
- From: Tomeh, Husam
- Re: PostgreSQL Caching
- Prev by Date: Re: simple case using index on windows but not on linux
- Next by Date: Re: simple case using index on windows but not on linux
- Previous by thread: Re: PostgreSQL Caching
- Next by thread: Re: BUG #2658: Query not using index
- Indexes: