| From: | Jan Wieck <jan(at)wi3ck(dot)info> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Craig Ringer <craig(at)2ndquadrant(dot)com> |
| Cc: | Marko Tiikkaja <marko(at)joh(dot)to>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: proposal: plpgsql - Assert statement |
| Date: | 2014-09-14 18:49:32 |
| Message-ID: | 5415E33C.4030003@wi3ck.info |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 09/14/2014 02:25 PM, Pavel Stehule wrote:
> a) Isn't possible handle a assertion exception anywhere .. it enforce
> ROLLBACK in 100%
>
> b) Assertions should be disabled globally .. I am not sure, it it is a
> good idea, but I can understand so some tests based on queries to data
> can be performance issue.
>
> Important question is a relation assertations and exceptions. Is it only
> shortcut for exception or some different?
I think that most data integrity issues can be handled by a well
designed database schema that uses UNIQUE, NOT NULL, REFERENCES and
CHECK constraints. Assertions are usually found inside of complex code
constructs to check values of local variables. I don't think it is even
a good idea to implement assertions that can query arbitrary data.
Jan
--
Jan Wieck
Senior Software Engineer
http://slony.info
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alexander Korotkov | 2014-09-14 19:34:26 | Re: KNN-GiST with recheck |
| Previous Message | Pavel Stehule | 2014-09-14 18:25:23 | Re: proposal: plpgsql - Assert statement |