Re: Postgresql the right tool (queue using advisory_locks + long transactions) - Mailing list pgsql-general

From Hannes Erven
Subject Re: Postgresql the right tool (queue using advisory_locks + long transactions)
Date
Msg-id 535D7174.1040006@erven.at
Whole thread Raw
In response to Re: Postgresql the right tool (queue using advisory_locks + long transactions)  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Postgresql the right tool (queue using advisory_locks + long transactions)  (John R Pierce <pierce@hogranch.com>)
Re: Postgresql the right tool (queue using advisory_locks + long transactions)  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
Hi,


On 2014-04-27 21:53, Tom Lane wrote:
 >
> Sitting on an open transaction for hours would be a bad idea.

I'm wondering why this is and what the consequences might be - I
thought, the MVCC model would handle that rather well?

Could please someone elaborate on this or provide some pointer? Thanks!


Best regards,

    -hannes



pgsql-general by date:

Previous
From: David G Johnston
Date:
Subject: Re: Postgresql the right tool (queue using advisory_locks + long transactions)
Next
From: Dorian Hoxha
Date:
Subject: Re: Re: Postgresql the right tool (queue using advisory_locks + long transactions)