On Thu, 2020-04-16 at 09:29 +0800, Jeremy Kerr wrote:
> On patchwork.ozlabs.org, we see a lot of noise in the postgres logs, due
> to INSERTs with duplicate values for (project,msgid) keys. Patchwork's
> strategy for catching the resulting IntegrityError means that each of
> these is logged.
>
>
On patchwork.ozlabs.org, we see a lot of noise in the postgres logs, due
to INSERTs with duplicate values for (project,msgid) keys. Patchwork's
strategy for catching the resulting IntegrityError means that each of
these is logged.
Instead, this change moves to an atomic select -> insert for the
