BUG #12127: could not stat file - Mailing list pgsql-bugs

From s.beer@pyton.nl
Subject BUG #12127: could not stat file
Date
Msg-id 20141202105944.2567.12489@wrigleys.postgresql.org
Whole thread Raw
List pgsql-bugs
The following bug has been logged on the website:

Bug reference:      12127
Logged by:          Stefan Beer
Email address:      s.beer@pyton.nl
PostgreSQL version: 9.3.1
Operating system:   Win2008R2
Description:

When I try to create a statistics report for one of my TableSpaces (both via
PgAdmin AND via the pgsql dll) I get an error: "could not stat file
[xyz]_fsm"

Meanwhile I have proven that this error is due to open connections to the
database on this tablespace. If I drop all open connections to the database,
the stats are working; as soon the clients connecting again, I get the error
again. It's 100% reproducible. I guess the tablespace stats/reports should
also work while heavy traffic on the database, so I'm sending you this bug
report.

pgsql-bugs by date:

Previous
From: marcin.ogorzalek@jmkcomputerate.pl
Date:
Subject: BUG #12126: Empty tsvector as output of to_tsvector function
Next
From: "Moppel, Kaarel"
Date:
Subject: "Drop index concurrently" leaving behind invalid indexes