| From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
|---|---|
| To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, Jiří Hlinka <jiri(dot)hlinka(at)gmail(dot)com> |
| Cc: | "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Deadlock detected after pg_repack receives SIGINT |
| Date: | 2015-11-04 02:48:18 |
| Message-ID: | 563971F2.2040500@BlueTreble.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/3/15 7:44 AM, Michael Paquier wrote:
> I doubt there is anything involving Postgres here. It seems that some
> process is still holding a lock on a relation that is being dropped,
> caused by a race condition in pg_repack code.
>
>> >PS: I was trying a mailing list of pg_repack
>> >(http://lists.pgfoundry.org/pipermail/reorg-genera) and github without any
>> >notice. If there is better place to ask, tell me, please.
> I guess you should let those folks time to answer. If I were you I'd
> begin first by letting more time for the repack operation to complete.
Make sure you're on the latest version too. There were some recent
commits aimed at fixing some race conditions.
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2015-11-04 03:05:19 | Re: MinGW-W64 compile error |
| Previous Message | Adrian Klaver | 2015-11-04 00:38:30 | Re: Check constraint and at least two rows |