On 11/18/15 2:42 PM, Jeff Janes wrote:
But he already knows it has race conditions. That is why he included
retry logic, to deal with those conditions.
From the sounds of it there's no retry loop, which means there's still
a race condition (data is deleted after insert fails but before update
On Wed, Nov 18, 2015 at 9:35 AM, Jim Nasby wrote:
> On 11/17/15 5:33 PM, anj patnaik wrote:
>>
>> The pg log files apparently log error lines every time a user inserts a
>> duplicate. I implemented a composite primary key and then when I see the
>> exception in my client app I update the row with
On 11/17/15 5:33 PM, anj patnaik wrote:
The pg log files apparently log error lines every time a user inserts a
duplicate. I implemented a composite primary key and then when I see the
exception in my client app I update the row with the recent data.
however, I don't want the log file to fill ou
On 11/17/2015 03:33 PM, anj patnaik wrote:
The pg log files apparently log error lines every time a user inserts a
duplicate. I implemented a composite primary key and then when I see the
exception in my client app I update the row with the recent data.
however, I don't want the log file to fill
The pg log files apparently log error lines every time a user inserts a
duplicate. I implemented a composite primary key and then when I see the
exception in my client app I update the row with the recent data.
however, I don't want the log file to fill out with these error messages
since it's han
