| From: | hubert depesz lubaczewski <depesz(at)gmail(dot)com> |
|---|---|
| To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: deadlock in single-row select-for-update + update scenario? How could it happen? |
| Date: | 2014-08-22 17:15:41 |
| Message-ID: | CAKrjmhdm-7a4Og_y8=MRUzs7NkK4t+iPG14bX-svTBca44a1oA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Fri, Aug 22, 2014 at 6:45 PM, Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> So process 66017 and 66014 are blocking each because they are running the
> exact same queries. The interesting part is the process with the lower pid
> is starting later then the none with the higher pid.
>
Locking is obvious. But why deadlock? There is just single row, and it
shouldn't be able to deadlock on it?!
> So what exactly is 'importer' and what does it do?
>
Some software written by some guy. Runs lots of queries, but the only
problem we have is with these transactions.
> Also what is this (59303)?
>
log_line_prefix is '%m %r %p %u %d ' so it's port number.
depesz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2014-08-22 17:20:10 | Re: deadlock in single-row select-for-update + update scenario? How could it happen? |
| Previous Message | Jeff Janes | 2014-08-22 16:55:27 | Re: deadlock in single-row select-for-update + update scenario? How could it happen? |