Re: [GENERAL] Block duplications in a shared buffers - Mailing list pgsql-general

From Tom Lane
Subject Re: [GENERAL] Block duplications in a shared buffers
Date
Msg-id 12618.1510068465@sss.pgh.pa.us
Whole thread Raw
In response to [GENERAL] Block duplications in a shared buffers  (pinker <pinker@onet.eu>)
Responses Re: [GENERAL] Block duplications in a shared buffers  (pinker <pinker@onet.eu>)
Re: [GENERAL] Block duplications in a shared buffers  (pinker <pinker@onet.eu>)
List pgsql-general
pinker <pinker@onet.eu> writes:
> I was analysing shared buffers content and noticed that exactly the same
> disk block appears there many times with different or the same usagecount.

Postgres would be completely broken if that were true, because
modifications made to one copy would fail to propagate to other copies.
I don't know where your data came from, but it can't be an accurate
representation of the instantaneous state of the buffer cache.

... actually, after looking at your query, I wonder whether the issue
is that you're failing to include database and tablespace in the
grouping key.  relfilenode isn't guaranteed unique across directories.
The fork number can matter, too.
        regards, tom lane


-- 
Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general

pgsql-general by date:

Previous
From: pinker
Date:
Subject: [GENERAL] Block duplications in a shared buffers
Next
From: Alvaro Herrera
Date:
Subject: Re: [GENERAL] Naming conventions for column names