| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: patch for 9.2: enhanced errors |
| Date: | 2011-07-18 20:27:52 |
| Message-ID: | 5415.1311020872@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> writes:
> so for example, NULL or DOMAIN constraints doesn't affect a
> COLUMN_NAME? These constraints has no name.
Well, the executor's NOT NULL tests could certainly be extended to emit
COLUMN_NAME --- I don't see any logical or implementation problem with
that, even if it seems to be outside the scope of what the standard says
to use the field for. But let's not get into modifying the system
catalogs to produce error fields that are not required by the standard.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kohei KaiGai | 2011-07-18 20:48:13 | Re: [v9.1] sepgsql - userspace access vector cache |
| Previous Message | Robert Haas | 2011-07-18 20:26:07 | Re: [v9.1] sepgsql - userspace access vector cache |