Re: big select is resulting in a large amount of disk writing by kjournald

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

 



Greg Smith wrote:
Joseph S wrote:
So I run "select count(*) from large_table" and I see in xosview a solid block of write activity. Runtime is 28125.644 ms for the first run. The second run does not show a block of write activity and takes 3327.441 ms
http://wiki.postgresql.org/wiki/Hint_Bits


Hmm. A large select results in a lot of writes? This seems broken. And if we are setting these hint bits then what do we need VACUUM for? Is there any way to tune this behavior? Is there any way to get stats on how many rows/pages would need hint bits set?

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

[Postgresql General]     [Postgresql PHP]     [PHP Users]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Yosemite]

  Powered by Linux