Re: [PATCH] SQL assertions prototype - Mailing list pgsql-hackers

From Andres Freund
Subject Re: [PATCH] SQL assertions prototype
Date
Msg-id 20131218113911.GC5224@alap2.anarazel.de
Whole thread Raw
In response to Re: [PATCH] SQL assertions prototype  (Heikki Linnakangas <hlinnakangas@vmware.com>)
Responses Re: [PATCH] SQL assertions prototype
List pgsql-hackers
On 2013-12-18 13:07:51 +0200, Heikki Linnakangas wrote:
> Here's another idea that doesn't involve SSI:
> 
> At COMMIT, take a new snapshot and check that the assertion still passes
> with that snapshot. Now, there's a race condition, if another transaction is
> committing at the same time, and performs the same check concurrently. That
> race condition can be eliminated by holding an exclusive lock while running
> the assertion, until commit, effectively allowing the assertion to be
> checked by only one transaction at a time.
> 
> I think that would work, and would be simple, although it wouldn't scale too
> well.

It probably would also be very prone to deadlocks.

Greetings,

Andres Freund

-- Andres Freund                       http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services



pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: [PATCH] SQL assertions prototype
Next
From: Ashutosh Bapat
Date:
Subject: Re: Example query causing param_info to be set in plain rel path