diff options
| author | Tom Lane <tgl@sss.pgh.pa.us> | 2013-11-07 14:41:39 -0500 |
|---|---|---|
| committer | Tom Lane <tgl@sss.pgh.pa.us> | 2013-11-07 14:41:39 -0500 |
| commit | df5d5f1dc75137db36099eb6a3759bde678828ad (patch) | |
| tree | be39557d0d0d44d8c702ef0b5405c99ef64cecbe /src/backend/parser/parse_node.c | |
| parent | 5d0731da521f090f80ea39529fe274ac6d6bffa1 (diff) | |
| download | postgresql-df5d5f1dc75137db36099eb6a3759bde678828ad.tar.gz postgresql-df5d5f1dc75137db36099eb6a3759bde678828ad.zip | |
Prevent display of dropped columns in row constraint violation messages.
ExecBuildSlotValueDescription() printed "null" for each dropped column in
a row being complained of by ExecConstraints(). This has some sanity in
terms of the underlying implementation, but is of course pretty surprising
to users. To fix, we must pass the target relation's descriptor to
ExecBuildSlotValueDescription(), because the slot descriptor it had been
using doesn't get labeled with attisdropped markers.
Per bug #8408 from Maxim Boguk. Back-patch to 9.2 where the feature of
printing row values in NOT NULL and CHECK constraint violation messages
was introduced.
Michael Paquier and Tom Lane
Diffstat (limited to 'src/backend/parser/parse_node.c')
0 files changed, 0 insertions, 0 deletions