VACUUM touching file but not updating relation - Mailing list pgsql-general

From Thom Brown
Subject VACUUM touching file but not updating relation
Date
Msg-id CAA-aLv7=_b68nzKaeiygT2gePNX_LaUXV8sr4YYFS6zu2Hzv_Q@mail.gmail.com
Whole thread Raw
Responses Re: VACUUM touching file but not updating relation  (Thom Brown <thom@linux.com>)
List pgsql-general
Hi,

I just noticed that the VACUUM process touches a lot of relations
(affects mtime) but for one file I looked at, it didn't change.  This
doesn't always happen, and many relations aren't touched at all.

I had the following relation:

-rw-------  1 thom  staff      40960 13 Oct 16:06 11946

Ran MD5 over the file:

MD5 (11946) = d6626f930f1fb6d77c3907d3279fe693

Then VACUUM ANALYSE'd all databases in full.

This relation was supposedly affected:

-rw-------  1 thom  staff      40960 14 Oct 11:27 11946

But then I ran MD5 back over it:

MD5 (11946) = d6626f930f1fb6d77c3907d3279fe693

This is the same as before.  What is it doing?  Does this happen
often?  And I can't find out what this particular OID relates to
either.

I'm using 9.2devel btw.

--
Thom Brown
Twitter: @darkixion
IRC (freenode): dark_ixion
Registered Linux user: #516935

EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

pgsql-general by date:

Previous
From: Kalai R
Date:
Subject: dll files missing in postgrsql bin folder in Windows
Next
From: Alban Hertroys
Date:
Subject: Re: Slow query: select * order by XXX desc offset 10 limit 10