| From: | Gregory Stark <stark(at)enterprisedb(dot)com> |
|---|---|
| To: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Question about debugging bootstrapping and catalog entries |
| Date: | 2006-12-18 11:35:44 |
| Message-ID: | 87odq1bfn3.fsf@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
--
Gregory Stark
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Martijn van Oosterhout | 2006-12-18 11:45:15 | Re: Question about debugging bootstrapping and catalog entries |
| Previous Message | Oleg Bartunov | 2006-12-18 11:33:24 | Re: quoting problem |