Received: from maia.hub.org (maia-3.hub.org [200.46.204.243]) by mail.postgresql.org (Postfix) with ESMTP id 962B71337BF2; Tue, 3 May 2011 08:12:57 -0300 (ADT) Received: from mail.postgresql.org ([200.46.204.86]) by maia.hub.org (mx1.hub.org [200.46.204.243]) (amavisd-maia, port 10024) with ESMTP id 24315-01-3; Tue, 3 May 2011 11:12:50 +0000 (UTC) X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 X-Greylist: domain auto-whitelisted by SQLgrey-1.7.6 Received: from mail-vw0-f46.google.com (mail-vw0-f46.google.com [209.85.212.46]) by mail.postgresql.org (Postfix) with ESMTP id 099D11337CCA; Tue, 3 May 2011 07:54:33 -0300 (ADT) Received: by vws1 with SMTP id 1so4885987vws.19 for ; Tue, 03 May 2011 03:54:34 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=G7Y5sbB5/VDOfufNw89Pp4HmWd1fX/YZvSzFuoCVKVI=; b=g+6J4/RFVuqD4G2hs+F1+/nUfcuwMKGUjdiwzMfuWuVbYOLeNXUqShr110rawI2RE+ hsTj6g+xbBXwwSED8JckENDDPQXzKEy5yUmsmkqa3+W4+wcEcszh1ivcUOTPLBptMQ2T ioUoj4/iOqA2kNXX/+sQr/FgGEaDNMcsT6ojc= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=Z+1MV+YkZUduN2cj6mcAOA0jNJQFYrdLgBtZ4F3/qZxYVf2lbeu2Ilj3WFvCv8oe4s NiXroWE/sgCkkbUVxZhIfJVozIZZvjCeNBDb95qg8YZZFDRmW+Vjmuve75rYTZN7+n5X rdPD65CMvaE49yDPmk0xcKZ4wSbuJLPgkKRhQ= MIME-Version: 1.0 Received: by 10.52.76.193 with SMTP id m1mr1599670vdw.204.1304420074206; Tue, 03 May 2011 03:54:34 -0700 (PDT) Received: by 10.52.109.99 with HTTP; Tue, 3 May 2011 03:54:34 -0700 (PDT) Date: Tue, 3 May 2011 16:24:34 +0530 Message-ID: Subject: Can we Flush the Postgres Shared Memory ? From: raghu ram To: pgsql-admin@postgresql.org, pgsql-general@postgresql.org, pgsql novice Content-Type: multipart/alternative; boundary=bcaec501603b29361904a25cf754 X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=-1.897 tagged_above=-10 required=5 tests=BAYES_00=-1.9, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RFC_ABUSE_POST=0.001 X-Spam-Level: X-Archive-Number: 201105/17 X-Sequence-Number: 37454 --bcaec501603b29361904a25cf754 Content-Type: text/plain; charset=ISO-8859-1 Respected Committers, It may be a silly question, still out of curiosity I want to know, is there any possible way to flush the Postgres Shared Memory without restarting the cluster. In Oracle, we can flush the SGA, can we get the same feature here.. Thanks in Advance. Regards Raghu Ram EnterpriseDB Corporation --bcaec501603b29361904a25cf754 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Respected=A0Committers,

It may be a silly question, stil= l out of curiosity I want to know, is there any possible way to flush the P= ostgres Shared Memory without restarting the cluster.

In Oracle, we can flush the SGA, can we get the same feature here..

Thanks in Advance.

Regards<= /div>
Raghu Ram
EnterpriseDB Corporation
--bcaec501603b29361904a25cf754--