From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(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:53:40 |
Message-ID: | CAHyXU0wDj7WXY672TfmQJtjG6R4QwGH454jdEwhMNQiwx52UwQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 14, 2015 at 6:50 PM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> This is great, but it's not exactly clear which bt_page_items() page
> is which - some are skipped, but I can't be sure which. Would you mind
> rewriting that query to indicate which block is under consideration by
> bt_page_items()?
yeah. via:
cds2=# \copy (select s as page, (bt_page_items('pg_class_oid_index',
s)).* from generate_series(1,12) s) to '/tmp/page_items.csv' csv
header;
merlin
Attachment | Content-Type | Size |
---|---|---|
page_items.csv | text/csv | 24.9 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2015-01-15 01:20:41 | Re: Turning recovery.conf into GUCs |
Previous Message | Peter Geoghegan | 2015-01-15 00:50:14 | Re: hung backends stuck in spinlock heavy endless loop |