SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-10-2008, 11:11 AM
| ||||
| ||||
 BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue The following bug has been logged online: Bug reference: 3707 Logged by: Rene Gollent Email address: rgollent@asteriasgi.com PostgreSQL version: 8.1.4 Operating system: Linux (Gentoo) Description: failure cases in reindex don't always report enough information to diagnose the issue Details: If you issue a REINDEX DATABASE, which then fails due to db corruption (i.e. could not create index due to duplicate values), the resulting error message only specifies: ERROR: could not create unique index DETAIL: Table contains duplicated values. without telling you what table actually triggered the error. It *can* be tracked down by manually looking up the oid of the last table that was successfully indexed and manually iterating from there, but it'd be nice to know directly. ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly      |
|
04-10-2008, 11:11 AM
| ||||
| ||||
| Re: BUG #3707: failure cases in reindex don't always report enough information to diagnose the issue "Rene Gollent" <rgollent@asteriasgi.com> writes: > If you issue a REINDEX DATABASE, which then fails due to db corruption (i.e. > could not create index due to duplicate values), the resulting error message > only specifies: > ERROR: could not create unique index > DETAIL: Table contains duplicated values. Hmm. It would be fairly easy to mention the index name here (less so to mention the table name, but I think you'd really need to know which index is the problem, anyway). ISTR that when this error message was written the index *wasn't* known at the place where the message was being emitted, but we do have it now ... regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
 |
« BUG #3362: xlog corruption just after initdb on irix
|
Fw: BUG #3695: Pgsql does not report non existing function »
| Thread Tools | |
| Display Modes | |
Linear Mode
|
|
All times are GMT. The time now is 10:30 AM.
