diff options
author | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-14 19:02:30 -0400 |
---|---|---|
committer | Tom Lane <tgl@sss.pgh.pa.us> | 2018-04-14 19:02:30 -0400 |
commit | b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e (patch) | |
tree | 7b346a2bac678631de3d1a6b63b9be9690d4ef72 /src/backend/commands/trigger.c | |
parent | 50c6bb022475bd9ad9c73e3b68b5152db5163b22 (diff) | |
download | postgresql-b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e.tar.gz postgresql-b39fd897e0398a6bdc6552daa7cacdf9c0e46d7e.zip |
Improve regression test coverage of expand_tuple().
I was dissatisfied with the code coverage report for expand_tuple() in the
wake of commit 7c44c46de: while better than no coverage at all, it was
still not exercising the core function of inserting out-of-line default
values, nor was the HeapTuple-output path covered. So far as I can find,
the only code path that reaches the latter at present is EvalPlanQual
fetches for non-locked tables. Hence, extend eval-plan-qual.spec to
test cases where out-of-line defaults must be inserted into a tuple
fetched from a non-locked table.
Discussion: https://postgr.es/m/87woxi24uw.fsf@ansel.ydns.eu
Diffstat (limited to 'src/backend/commands/trigger.c')
0 files changed, 0 insertions, 0 deletions