Re: REINDEX deadlock - Postgresql -9.1

From: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>
To: Anoop K <anoopk6(at)gmail(dot)com>
Cc: Albe Laurenz <laurenz(dot)albe(at)wien(dot)gv(dot)at>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>, Venkatraju TV <venkatraju(at)gmail(dot)com>
Subject: Re: REINDEX deadlock - Postgresql -9.1
Date: 2013-02-07 11:11:01
Message-ID: CAOR=d=28uL9o1OB=uUMn_2j1s5fG0N2xUJe=qb=J6Zei==9-kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Note that if those processes use persistent connections you'll need to
restart them to free up the connections. In the meantime you can use
the step of renaming your superuser account. Then cutting all
superuser conns and turning off superuser of postgres user
temporarily. I wouldn't do this all night or anything, as autovac
usually connects as postgres to do its thing.

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Jasen Betts 2013-02-07 11:17:07 Re: DEFERRABLE NOT NULL constraint
Previous Message Anoop K 2013-02-07 11:09:30 Re: REINDEX deadlock - Postgresql -9.1