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

From Andres Freund
Subject Re: [PATCH] SQL assertions prototype
Date
Msg-id 20131218194506.GA6038@alap2.anarazel.de
Whole thread Raw
In response to Re: [PATCH] SQL assertions prototype  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: [PATCH] SQL assertions prototype
Re: [PATCH] SQL assertions prototype
List pgsql-hackers
On 2013-12-18 16:39:58 -0300, Alvaro Herrera wrote:
> Andres Freund wrote:
> > It would only force serialization for transactions that modify tables
> > covered by the assert, that doesn't seem to bad. Anything covered by an
> > assert shoulnd't be modified frequently, otherwise you'll run into major
> > performance problems.
> 
> Well, as presented there is no way (for the system) to tell which tables
> are covered by an assertion, is there?  That's my point.

Well, the patch's syntax seems to only allow to directly specify a SQL
query to check - we could iterate over the querytree to gather all
related tables and reject any function we do not understand.

Greetings,

Andres Freund

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



pgsql-hackers by date:

Previous
From: Kevin Grittner
Date:
Subject: Re: [PATCH] SQL assertions prototype
Next
From: Jim Nasby
Date:
Subject: Re: [PATCH] SQL assertions prototype