From: Scott Marlowe <scott.marlowe@gmail.com>
To: Darren Reed <darrenr+postgres@fastmail.net>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Joshua D. Drake <jd@commandprompt.com>
Cc: pgsql-admin@postgresql.org
Subject: Re: Is my database now too big?
Date: Mon, 15 Oct 2007 23:03:14 -0500
Message-ID: <dcc563d10710152103x7b3b2f68q2e133172731f7c0a@mail.gmail.com> (raw)
In-Reply-To: <471435D1.4030806@fastmail.net>
References: <1191730382.18880.1214536197@webmail.messagingengine.com>
<dcc563d10710070713q6aa1fbfdqe8f07e5356d39d41@mail.gmail.com>
<47097EA7.902@fastmail.net>
<dcc563d10710071803ia92a046neef1296999173d13@mail.gmail.com>
<4712D97E.7010004@fastmail.net>
<4712E15B.8000405@fastmail.net>
<17093.1192464190@sss.pgh.pa.us>
<4713CA8C.5020303@fastmail.net>
<dcc563d10710151346w430da8a2s265bd8e129ee7d@mail.gmail.com>
<471435D1.4030806@fastmail.net>
On 10/15/07, Darren Reed <darrenr+postgres@fastmail.net> 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?
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, darrenr+postgres@fastmail.net, tgl@sss.pgh.pa.us, jd@commandprompt.com
Subject: Re: Is my database now too big?
In-Reply-To: <dcc563d10710152103x7b3b2f68q2e133172731f7c0a@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox