Re: BUG #12718: Apparent LWlock Problem Perhaps With Page Cleanup

From: Peter Geoghegan <pg(at)heroku(dot)com>
To: charles(dot)harwood(at)zuerchertech(dot)com
Cc: pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: BUG #12718: Apparent LWlock Problem Perhaps With Page Cleanup
Date: 2015-01-31 00:41:15
Message-ID: CAM3SWZQ0BZXwWQJW5EQ6N=P8=M6kn1PTp9yi3WKhVxjpXP7KXg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Fri, Jan 30, 2015 at 2:14 PM, <charles(dot)harwood(at)zuerchertech(dot)com> wrote:
> Many postgres worker processes stopped responding. They continued to be in
> state 'active' and not 'waiting' for hours. Each query was on the table
> that an autovacuum process was also hung on processing and was the oldest
> active transaction on.

Was pg_upgrade run on this database at some point [1]?

I foresee more problems here...

[1] http://www.postgresql.org/message-id/20140825225029.2536.5315@wrigleys.postgresql.org
--
Peter Geoghegan

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message hans 2015-01-31 17:37:38 BUG #12721: psql -a does not preserve empty lines between SELECTs
Previous Message charles.harwood 2015-01-30 22:14:45 BUG #12718: Apparent LWlock Problem Perhaps With Page Cleanup