On Fri, Mar 26, 2010 at 7:57 PM, Richard Yen <d...@richyen.com> wrote: > Note that it is constantly paging in, but never paging out. This would > indicate that it's constantly reading from swap, but never writing out to it. > Why would postgres do this? (postgres is pretty much the only thing running > on this machine). > > I'm planning on lowering the shared_buffers to a more sane value, like 25GB > (pgtune recommends this for a Mixed-purpose machine) or less (pgtune > recommends 14GB for an OLTP machine). However, before I do this (and > possibly resolve the issue), I was hoping to see if anyone would have an > explanation for the constant reading from swap, but never writing back.
Reading a page in from swap still leaves that data on the disk. So it may be that you're reading in pages from disk, not modifying them, discarding them (without any need to write them out since they're still on disk), and then reading them in again when they're accessed again. ...Robert -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
