SEO
vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
04-24-2008, 06:12 PM
| ||||
| ||||
 Re: ERROR: failed to re-find parent key in "sl_seqlog_idx"for deletion target John Parnefjord wrote: > Hi! > > Hope anyone can shed some light on this. I was struck by the > following error in the slony log but I believe it's not a slony > error, rather that slony triggers an error in PostgreSQL. The error > message is: Correct, that's not a backend error. > cleanupThread: vacuum analyze sl_seqlog; - ERROR: failed to re-find > parent key in "sl_seqlog_idx" for deletion target > > I've tried to find some posts about it and I could only find one post > where Tom states that reindexing should do the trick, but there is no > answer that reindexing did solve the case. The post is here: > http://archives.postgresql.org/pgsql...8/msg00035.php > > Well, it is supposed to have been fixed to version 8.2, but it's a > PostgreSQL 8.2.4 x86_64 server running on Debian that triggers the > error. Hi! Please copy out the files as requested in that email - I'm sure Tom is still interested in debugging it to find the issue. After that, try a REINDEX to see if it solves your problem. And while you're at it, you guys should be at 8.2.7, not 8.2.4.. :-P There are some index fixes between those versions (specifically in 8.2.5), but I don't know the details of them enough to say if this could be the problem you're hitting. //Magnus -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs      |
|
04-24-2008, 06:12 PM
| ||||
| ||||
| Re: ERROR: failed to re-find parent key in "sl_seqlog_idx"for deletion target John Parnefjord wrote: > > Please copy out the files as requested in that email - I'm sure Tom > > is still interested in debugging it to find the issue. After that, > > try a REINDEX to see if it solves your problem. > > Ok, see the snippets below. I just cut them from the PgAdminIII > interface. Drop me a mail if you need more info. Ok, misunderstandment. What's needed are the actual data files, not the definition of the tables. That is, the files under $PGDATA that contains the table and it's indexes. Can't send those on-list, they're too large, but if you can put together a .tar.gz for someone to look at. Before you send it, we'll want to check with Tom that he's still interested in looking at it :-) > > And while you're at it, you guys should be at 8.2.7, not 8.2.4.. :-P > > Yes, you're right. But as we are trying out tsearch2 for full text > searching it might just as well be a good idea to go straight to 8.3 > during the summer. Probably, yes. //Magnus -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs |
 |
« BUG #4113: server closed the connection unexpectedly
|
BUG #4122: ./postres 'restart' does not start server with same options as 'start' does »
| Thread Tools | |
| Display Modes | |
Linear Mode
| |
All times are GMT. The time now is 01:20 PM.
