Harald Armin Massa wrote:
> Alvaro,
>
> > How many database-wide vacuums did you run during these 9 months? I'm
> > smelling transaction Id wraparound in pg_class or some other system
> > catalog.
>
> "database wide" vacuums have been very very seldom; I fear the only one was
> at initial db bul
Alvaro,How many database-wide vacuums did you run during these 9 months? I'm
smelling transaction Id wraparound in pg_class or some other systemcatalog.This has been known to happen. Please see the archives."database wide" vacuums have been very very seldom; I fear the only one was at initial db
Harald Armin Massa wrote:
> Hello QuingQing,
>
> > What is your file system, NTFS or FAT32? Is that table newly created?
>
> File System is NTFS. That table was created with database installation,
> which was short after after release of PostgreSQL 8.0 - so that database was
> in use for > 9 mont
Hello QuingQing,What is your file system, NTFS or FAT32? Is that table newly created?
File System is NTFS. That table was created with database installation, which was short after after release of PostgreSQL 8.0 - so that database was in use for > 9 months. That table is a central table of the appl
On Wed, 23 Nov 2005, Harald Armin Massa wrote:
>
> no, it is definitely NOT a temp table. I know which table it is,
> because: that "could not open relation ..." error message was exactly
> provokable with "select * from repofeld", which is one of my tables in
> that database.
>
What is your file
Quingqing,
no, it is definitely NOT a temp table. I know which table it is, because:
that "could not open relation ..." error message was exactly provokable
with "select * from repofeld", which is one of my tables in that
database.
(And that was the way it was passed on to me: my application put
"Harald Armin Massa" <[EMAIL PROTECTED]> wrote
>
> 2005-11-21 09:45:50 ERROR: could not open relation 1663/17253/43471: No
> such
> file or directory
>
> My checking showed that... within directory data/base/17253 there is
> indeed
> no file named 43471; but ones named 43470,43472,43473 .
>
