[dead]

Nice - that's a good case for barriers too. When there's no row to SELECT FOR UPDATE against, you'd inject the barrier after acquiring the advisory lock and verify the second transaction blocks until the first commits.

▲

klysm 7 hours ago | parent | prev | next [-]

Seems like a good way to materialize the conflict.

▲

deepsun 7 hours ago | parent | prev [-]

I always did "INSERT ... ON CONFLICT DO NOTHING".

	▲	nurettin an hour ago \| parent [-]
		Does that queue when the table is locked? Or just skip writes entirely whenever there is a transaction?