| From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com>, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
| Cc: | Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, Kevin Grittner <kgrittn(at)ymail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH] SQL assertions prototype |
| Date: | 2014-01-05 20:10:46 |
| Message-ID: | 52C9BC46.1010505@gmx.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 12/18/13, 2:22 PM, 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.
I think that makes sense. If you want to use assertions, you need to
run in serializable mode, otherwise you get an error if you modify
anything covered by an assertion.
In the future, someone could enhance this for other isolation levels,
but as Josh has pointed out, that would likely just be reimplementing
SSI with big locks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2014-01-05 20:12:02 | Re: [PATCH] SQL assertions prototype |
| Previous Message | Robert Haas | 2014-01-05 19:52:44 | Re: [PATCH] Store Extension Options |