| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Andres Freund <andres(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: hung backends stuck in spinlock heavy endless loop |
| Date: | 2015-01-15 18:47:05 |
| Message-ID: | CAM3SWZTsnQnbyP=uXcdr9b8O8W8kKuyYxrnoGibCt2M1sX_ZJw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jan 15, 2015 at 6:02 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> Question: Coming in this morning I did an immediate restart and logged
> into the database and queried pg_class via index. Everything was
> fine, and the leftright verify returns nothing. How did it repair
> itself without a reindex?
Maybe the relevant WAL records are more or less correct, and recovery
restores the database to its correct state, as opposed to the state it
was actually in at the time of the crash due to a race condition or
whatever. Could you possibly send bt_page_items() against block 9 of
the index after recovery? It probably looks totally sane, but it would
be nice to be sure, if you happen to still have the data.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2015-01-15 18:53:24 | Re: hung backends stuck in spinlock heavy endless loop |
| Previous Message | Tom Lane | 2015-01-15 18:45:51 | Re: OOM on EXPLAIN with lots of nodes |