From: | Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Question about debugging bootstrapping and catalog |
Date: | 2006-12-18 12:51:24 |
Message-ID: | Pine.LNX.4.58.0612182350080.8629@linuxworld.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, 18 Dec 2006, Gregory Stark wrote:
>
> I've been fooling with catalog entries here and I've obviously done something
> wrong. But I'm a bit frustrated trying to debug initdb. Because of the way it
> starts up the database in a separate process I'm finding it really hard to
> connect to the database and get a backtrace. And the debugging log is being
> spectacularly unhelpful in not telling me where the problem is.
>
> Are there any tricks people have for debugging bootstrapping processing? I
> just need to know what index it's trying to build here and that should be
> enough to point me in the right direction:
>
> creating template1 database in /var/tmp/db7/base/1 ... FATAL: could not create unique index
> DETAIL: Table contains duplicated values.
>
Not much fun. Run src/include/catalog/duplicate_oids first.
Thanks,
Gavin
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2006-12-18 13:03:34 | Re: Question about debugging bootstrapping and catalog entries |
Previous Message | Martijn van Oosterhout | 2006-12-18 12:28:25 | Re: Question about debugging bootstrapping and catalog entries |