| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | 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 00:34:52 |
| Message-ID: | CAM3SWZR5qAn+6AeSQkkMOcxbYiKZr+gdPx0R5kD0w7iUWVi_jA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 14, 2015 at 4:26 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
> The index is the oid index on pg_class. Some more info:
>
> *) temp table churn is fairly high. Several dozen get spawned and
> destroted at the start of a replication run, all at once, due to some
> dodgy coding via dblink. During the replication run, the temp table
> churn rate drops.
>
> *) running btreecheck, I see:
I knew I wrote that tool for a reason. :-)
It would be great if I could get a raw dump of the index using
contrib/pageinspect at this juncture too, as already described.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Merlin Moncure | 2015-01-15 00:36:39 | Re: hung backends stuck in spinlock heavy endless loop |
| Previous Message | Tom Lane | 2015-01-15 00:31:18 | Re: s_lock.h default definitions are rather confused |