From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | pg noob <pgnube(at)gmail(dot)com> |
Cc: | pgsql-performance(at)postgresql(dot)org |
Subject: | Re: pg_buffercache |
Date: | 2012-11-01 21:26:21 |
Message-ID: | CAHyXU0zTtZJ=rxXDTwoBxkb=BBcK36SVwyYfydiZ53__J0hUVw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-performance |
On Tue, Oct 30, 2012 at 1:34 PM, pg noob <pgnube(at)gmail(dot)com> wrote:
>
> Hi all,
>
> I was wondering if it is safe to install pg_buffercache on production
> systems?
Well, why wouldn't you expect it to be safe? Core extensions should
be mostly assumed safe unless there is a good reasons to believe
otherwise. That said, there may be some performance impacts, In
particular, take note:
"When the pg_buffercache view is accessed, internal buffer manager
locks are taken for long enough to copy all the buffer state data that
the view will display. This ensures that the view produces a
consistent set of results, while not blocking normal buffer activity
longer than necessary. Nonetheless there could be some impact on
database performance if this view is read often."
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Gunnar "Nick" Bluth | 2012-11-01 23:25:16 | Re: Re: Increasing work_mem and shared_buffers on Postgres 9.2 significantly slows down queries |
Previous Message | Marcos Ortiz | 2012-11-01 20:40:34 | Re: Re: Increasing work_mem and shared_buffers on Postgres 9.2 significantly slows down queries |