From: | Dave Cramer <pg(at)fastcrypt(dot)com> |
---|---|
To: | Paul Tomblin <ptomblin(at)gmail(dot)com> |
Cc: | pgsql-jdbc(at)postgresql(dot)org |
Subject: | Re: Atomic operations? |
Date: | 2008-03-18 14:17:52 |
Message-ID: | 845D8D6D-E1F8-4D8C-82B1-2EC3D3C4E6D0@fastcrypt.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc |
On 18-Mar-08, at 10:12 AM, Paul Tomblin wrote:
> On Tue, Mar 18, 2008 at 10:06 AM, Dave Cramer <pg(at)fastcrypt(dot)com>
> wrote:
>> On 18-Mar-08, at 9:40 AM, Paul Tomblin wrote:
>>> I'm doing a simple delete/insert on a table, rather than trying to
>>> figure out whether the row exists or not and then doing an update or
>>> an insert. But what I'm discovering is that every now and then I
>>> get
>>> a duplicate primary key exception, so I figure that two processes
>>> are
>>> doing the deletes and inserts and stomping on each other. So my
>>
>> Can't you just check the return value from the delete to see if
>> anything was deleted ?
>
> I'm not sure how that would help. If I do the delete and it didn't
> delete anything, that doesn't tell me if some other process inserted
> it in the meantime.
>
which ever process succeeds in deleting should do the insert.
Dave
>
>
>
> --
> For my assured failures and derelictions I ask pardon beforehand of my
> betters and my equals in my Calling here assembled, praying that in
> the hour of my temptations, weakness and weariness, the memory of this
> my Obligation and of the company before whom it was entered into, may
> return to me to aid, comfort and restrain.
From | Date | Subject | |
---|---|---|---|
Next Message | Dave Cramer | 2008-03-18 14:25:57 | Re: setQueryTimeout problem !?!?! |
Previous Message | Paul Tomblin | 2008-03-18 14:12:08 | Re: Atomic operations? |