From: | Andres Freund <andres(at)2ndquadrant(dot)com> |
---|---|
To: | hannes(dot)janetzek(at)gmail(dot)com |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #10542: infinite loop in index.c when trying to reindex system tables (probably corrupted db state) |
Date: | 2014-06-06 16:34:42 |
Message-ID: | 20140606163442.GE10482@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Hi,
On 2014-06-05 23:00:56 +0000, hannes(dot)janetzek(at)gmail(dot)com wrote:
> While trying to get our database working again after a forced shutdown the
> reindexing of the system tables in single user mode went into an infinite
> loop.
what happened in that infinite loop? The log excerpt below doesn't show
one? Is it constantly echoing a message?
could you explain how you got into the bad state? Are you using
fsync=off?
> I can just roughly guess that between the lines:
> https://github.com/postgres/postgres/blob/REL9_3_STABLE/src/backend/catalog/index.c#L2260-
> L2385
> the function is assuming that another process tries to delete a tuple that
> is about to be indexed (even though in single user mode this should probably
> not be possible)
We've recently fixed a bug around that - but I don't immediately see how
it could be applicable in that scenario.
Greetings,
Andres Freund
--
Andres Freund http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-06-06 16:47:27 | Re: BUG #8673: Could not open file "pg_multixact/members/xxxx" on slave during hot_standby |
Previous Message | kuladeepmca2007 | 2014-06-06 13:07:34 | BUG #10548: NpgsqlException - ERROR: 57014: canceling statement due to user request |