From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Xin Pan <panxin0718(at)gmail(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: replication optimization: page writes only at the slave |
Date: | 2012-12-10 23:01:07 |
Message-ID: | CA+Tgmoaa4CeepA-cS4PUWndBd6dF-PmOTM1eiOQ0f4jp+5S3Fw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Dec 10, 2012 at 10:56 AM, Xin Pan <panxin0718(at)gmail(dot)com> wrote:
> However, I still witness large amount of page writes.
> Can anyone tell where are the page writes come from?
Probably not without more details. Things like VACUUM, COPY, and
sequential scans use ring-buffers that are smaller than
shared_buffers, so you often see the cache fill up with your data only
slowly just after starting the database, but if the database really
fits in shared_buffers, you should eventually settle into a rhythm
where dirty buffers are written to disk only once per checkpoint
cycle.
You might want to monitor pg_stat_bgwriter.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Daniel Farina | 2012-12-10 23:15:29 | Re: Sketch of a Hook into the Logging Collector |
Previous Message | Andres Freund | 2012-12-10 22:42:25 | Re: [SPAM?]: Re: Support for REINDEX CONCURRENTLY |