Thread: Flush Shared Buffer Cache

Flush Shared Buffer Cache

From
Suvankar Roy
Date:

Hi,

Can anyone help me out with how to flush out Shared Buffer Cache in Postgres.

One way would be to restart the database, but I would like to avoid that.

Regards,

Suvankar Roy
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


Re: Flush Shared Buffer Cache

From
Chander Ganesan
Date:
Suvankar Roy wrote:
>
> Hi,
>
> Can anyone help me out with how to flush out Shared Buffer Cache in
> Postgres.
>
> One way would be to restart the database, but I would like to avoid that.
AFAIK, that's the only way.

Is there a reason that you need to dump the shared buffers?  Perhaps if
we knew what you were trying to accomplish we could provide you with a
suitable solution that doesn't require a restart...

--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Expert PostgreSQL, PostGIS, and other Open Source training delivered worldwide.


Re: Flush Shared Buffer Cache

From
Suvankar Roy
Date:

Hi Chander,

Actually I am trying to figure out how much execution time any query is taking is taking when executed for the first time.

Because once a query is executed for the first time, the query plan, data buffer is cached so subsequently time taken is much lower.

For this, I want to have the Shared buffer cache flushed to note the initial execution time.

Is my understanding correct here ?

Regards,

Suvankar Roy



Chander Ganesan <chander@otg-nc.com>

07/15/2009 08:48 PM

To
Suvankar Roy <suvankar.roy@tcs.com>
cc
pgsql-admin@postgresql.org
Subject
Re: [ADMIN] Flush Shared Buffer Cache





Suvankar Roy wrote:
>
> Hi,
>
> Can anyone help me out with how to flush out Shared Buffer Cache in
> Postgres.
>
> One way would be to restart the database, but I would like to avoid that.
AFAIK, that's the only way.

Is there a reason that you need to dump the shared buffers?  Perhaps if
we knew what you were trying to accomplish we could provide you with a
suitable solution that doesn't require a restart...

--
Chander Ganesan
Open Technology Group, Inc.
One Copley Parkway, Suite 210
Morrisville, NC  27560
919-463-0999/877-258-8987
http://www.otg-nc.com
Expert PostgreSQL, PostGIS, and other Open Source training delivered worldwide.


ForwardSourceID:NT00004B0E    
=====-----=====-----=====
Notice: The information contained in this e-mail
message and/or attachments to it may contain 
confidential or privileged information. If you are 
not the intended recipient, any dissemination, use, 
review, distribution, printing or copying of the 
information contained in this e-mail message 
and/or attachments to it are strictly prohibited. If 
you have received this communication in error, 
please notify us by reply e-mail or telephone and 
immediately and permanently delete the message 
and any attachments. Thank you


Re: Flush Shared Buffer Cache

From
"Kevin Grittner"
Date:
Suvankar Roy <suvankar.roy@tcs.com> wrote:

> Actually I am trying to figure out how much execution time any query
> is taking is taking when executed for the first time.
>
> Because once a query is executed for the first time, the query plan,
> data buffer is cached so subsequently time taken is much lower.
>
> For this, I want to have the Shared buffer cache flushed to note
> the initial execution time.
>
> Is my understanding correct here ?

Keep in mind that the OS cache will also normally have a significant
amount of PostgreSQL data cached.  For "uncached" timings, you will
need to purge this, too.  Of course, for real-life production
benchmarks the most meaningful timings are normally those taken within
your actual production mix, with all the caching and resource
competition which goes along with that.

-Kevin