On 10/15/07, Darren Reed <darrenr+postgres@xxxxxxxxxxxx> wrote:
> Scott Marlowe wrote:
> > ...
> >
> > Again, I'm kinda shooting in the dark here as you reveal more and more
> > what you are doing a little at a time. A test case that can invoke
> > this failure would be most useful.
> >
> After seeing this today:
> ERROR: duplicate key violates unique constraint "ers_pkey"
> ERROR: duplicate key violates unique constraint "foo_pkey"
> ERROR: duplicate key violates unique constraint "foo_pkey"
> ERROR: duplicate key violates unique constraint "foo_pkey"
> ERROR: duplicate key violates unique constraint "foo_pkey"
> ERROR: duplicate key violates unique constraint "foo_pkey"
> ERROR: could not open segment 1 of relation 1663/10793/2659 (target
> block 858862642): No such file or directory
> ERROR: could not open segment 1 of relation 1663/10793/2659 (target
> block 858862642): No such file or directory
> ERROR: could not open segment 1 of relation 1663/10793/2659 (target
> block 858862642): No such file or directory
> ERROR: could not open segment 1 of relation 1663/10793/2659 (target
> block 858862642): No such file or directory
> ...
>
> ...there was little or no activity during this time, apart from
> some inserts, maybe some selects, etc. Nothing that should
> have caused this kind of upset.
>
> There is a file that matches this:
> -rw------- 1 postgres wheel 57344 Oct 14 22:57
> /data/db/second/base/10793/2659
> but it isn't in the directory where I moved most of the indexes to:
> ls /data/index/ext/10793/
> 16390 16397 16399 16406 16407 16410 16414 16425 16434 16435
How, exactly, did you move those indexes?
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
