"Laurent Raufaste" <analogue@xxxxxxxx> writes: > All this make me think that PG was setting some bit on every row it > used, which caused this massive write activity (3MB/s) in the table > files. I'm talking about approx. 50 SELECT per second for a single > server. Well that's true it does. But only once per row. So analyze would have set the bit on every row. You could do the same thing with something ligter like "select count(*) from <table>". Tom's thinking was that you would only expect a high update rate for a short time until all those bits were set. Slony's inserts, updates, and deletes count as updates to the table as well. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com Ask me about EnterpriseDB's RemoteDBA services! -- Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance
