Mark Kirkwood wrote:
Simon Riggs wrote:
On Sun, 2009-01-04 at 21:03 +1300, Mark Kirkwood wrote:
bench=# \d history
Table "public.history"
Column | Type | Modifiers
--------+-----------------------------+-----------
tid | integer |
bid | integer |
aid | integer |
delta | integer |
mtime | timestamp without time zone |
filler | character(22) |
bench=# select now(),count(*) from history;
ERROR: could not open relation base/16384/16394: No such file or
directory
>From my recreating your test case, the oids are consistent with the
History table. So the cache looks good.
md.c should be cacheing the file descriptor so the second use of the
file should not be reopening it. I've not touched smgr/md so a missing
file error is a surprise.
I wonder if this is an error associated with large file handling and
file forks? Smells like an FSM or VM error.
Is the file actually missing? i.e. ls -l mydatadir/base/16384/16394*
Yeah -
$ ls -l $PGDATA/base/16384/16394*
ls: /data0/pgslave/8.4/base/16384/16394*: No such file or directory
This might be useful:
the other tables in the dataset (accounts, branches, tellers) all
behave as expected:
bench=# select now(),count(*) from branches;
now | count
-------------------------------+-------
2009-01-04 22:17:00.298597+13 | 100
(1 row)
I'm guessing something tied up with the fact that history has no rows to
start with...
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
