Search Postgresql Archives

Re: Why does a SELECT query cause "dirtied" buffers?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Why does a SELECT query cause "dirtied" buffers?
From: Justin Pryzby <pryzby@xxxxxxxxxxxxx>
Date: Fri, 27 Oct 2017 14:30:26 -0500
Cc: pgsql-general@xxxxxxxxxxxxxx
In-reply-to: <ot015g$ml7$1@blaine.gmane.org>
References: <ot015g$ml7$1@blaine.gmane.org>
User-agent: Mutt/1.5.23 (2014-03-12)

On Fri, Oct 27, 2017 at 09:24:40PM +0200, Thomas Kellerer wrote:
> Under which situation does a SELECT query change a block?

https://wiki.postgresql.org/wiki/Hint_Bits


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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

References:
- Why does a SELECT query cause "dirtied" buffers?
  - From: Thomas Kellerer

Prev by Date: Why does a SELECT query cause "dirtied" buffers?
Next by Date: Re: Where to find development builds of pg for windows
Previous by thread: Why does a SELECT query cause "dirtied" buffers?
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux