| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Maxim Boguk <maxim(dot)boguk(at)gmail(dot)com>, pgsql-bugs <pgsql-bugs(at)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
| Subject: | Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. |
| Date: | 2015-10-06 08:43:54 |
| Message-ID: | CAB7nPqSb=4GG_mi_D0hdXJKmhOcL+hGA61pU0jdCZJFRT4qTqw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
On Tue, Oct 6, 2015 at 2:10 AM, Jeff Janes wrote:
> I was assuming that the table being AccessExclusive locked and the table
> being VACUUMed were two different tables, which were done in two different
> processes on the master, which means that no re-ordering of WAL records
> would be necessary to hit this.
Right. This may be possible as well.
> Although I also haven't yet been able to reproduce the deadlock under this assumption.
Yeah, we are a bit blind here. Maxim, did you perform an operation on
master that took an exclusive lock on the relation involved here? Was
this relation a table, an index? If an index, what kind of index? I
think that such information may help us narrowing down a test case.
--
Michael
| From | Date | Subject | |
|---|---|---|---|
| Next Message | slava | 2015-10-06 18:56:02 | BUG #13664: pg_restore fails with -j parameter when restoring 9.1 db onto 9.5 alpha db |
| Previous Message | Jeff Janes | 2015-10-05 17:10:09 | Re: BUG #13657: Some kind of undetected deadlock between query and "startup process" on replica. |