Re: High concurrency same row (inventory) - Mailing list pgsql-performance

From Jean Baro
Subject Re: High concurrency same row (inventory)
Date
Msg-id CA+fQeemmZgztnq89G+y5qUuLz810BEfgE=opJemdAhm-voNe_w@mail.gmail.com
Whole thread Raw
In response to Re: High concurrency same row (inventory)  (Jean Baro <jfbaro@gmail.com>)
Responses Re: High concurrency same row (inventory)  (Jean Baro <jfbaro@gmail.com>)
List pgsql-performance
The UPDATE was something like:

UPDATE bucket SET qty_available = qty_available + 1 WHERE bucket_uid = 0940850938059380590

Thanks for all your help guys!

On Mon, Jul 29, 2019 at 9:04 PM Jean Baro <jfbaro@gmail.com> wrote:
All the failures come from the Bucket Table (see image below).

I don't have access to the DB, neither the code, but last time I was presented to the UPDATE it was changing (incrementing or decrementing) qty_available, but tomorrow morning I can be sure, once the developers and DBAs are back to the office. I know it's quite a simple UPDATE.

Table is called Bucket:
{autovacuum_vacuum_scale_factor=0.01}

Bucket.png


On Mon, Jul 29, 2019 at 3:12 PM Michael Lewis <mlewis@entrata.com> wrote:
Can you share the schema of the table(s) involved and an example or two of the updates being executed?
Attachment

pgsql-performance by date:

Previous
From: Jean Baro
Date:
Subject: Re: High concurrency same row (inventory)
Next
From: Jean Baro
Date:
Subject: Re: High concurrency same row (inventory)