Re: [BUGS] Status of issue 4593 - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [BUGS] Status of issue 4593
Date
Msg-id 496C8C7D.EE98.0025.0@wicourts.gov
Whole thread Raw
In response to Re: [BUGS] Status of issue 4593  (Josh Berkus <josh@agliodbs.com>)
Responses Re: [BUGS] Status of issue 4593  (Gregory Stark <stark@enterprisedb.com>)
List pgsql-hackers
>>> Josh Berkus <josh@agliodbs.com> wrote: 
> we'd break 100,000 existing Java applications if we changed the
error. 
In what way would an application want to treat deadlocks and update
conflicts differently?  Both result from conflicts with concurrent
transactions and can be retried automatically.  It seems like an
implementation detail with little chance of impact on applications to
me.  Can anyone provide a contrary example or argument?
-Kevin


pgsql-hackers by date:

Previous
From: Josh Berkus
Date:
Subject: Re: [BUGS] Status of issue 4593
Next
From: Gregory Stark
Date:
Subject: Re: [BUGS] Status of issue 4593