Skip site navigation (1) Skip section navigation (2)

Re: Re: [patch] Include detailed information about a row failing a CHECK constraint into the error message

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: <jkt(at)flaska(dot)net>,"Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Robert Haas" <robertmhaas(at)gmail(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Re: [patch] Include detailed information about a row failing a CHECK constraint into the error message
Date: 2011-11-29 20:24:40
Message-ID: 4ED4EB2802000025000435F2@gw.wicourts.gov (view raw or flat)
Thread:
Lists: pgsql-hackers
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
 
> I was wondering in particular whether it wouldn't be appropriate
> to include the same errdetail in ExecConstraints's other check,
> the one for null in not-null columns.  Arguably a not-null check
> is just a slightly optimized form of a CHECK constraint, and
> anyway if you think you need row identification info for a CHECK
> failure I don't see why you'd not want it for NOT NULL failure. 
> Comments?
 
Makes sense to me.
 
-Kevin

In response to

pgsql-hackers by date

Next:From: Bruce MomjianDate: 2011-11-29 20:34:40
Subject: Re: Inlining comparators as a performance optimisation
Previous:From: Tom LaneDate: 2011-11-29 20:09:59
Subject: Re: Re: [patch] Include detailed information about a row failing a CHECK constraint into the error message

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group