aboutsummaryrefslogtreecommitdiff
path: root/src/backend/executor/nodeResult.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2007-10-01 16:25:56 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2007-10-01 16:25:56 +0000
commitb526462f9e654149f9ee197a8b2d801c5a80e30e (patch)
tree3094d311bc02ed9b1f833d44ba6a874a26fed369 /src/backend/executor/nodeResult.c
parentb8ce3d34941c3801d4224c826db1953d34dc3385 (diff)
downloadpostgresql-b526462f9e654149f9ee197a8b2d801c5a80e30e.tar.gz
postgresql-b526462f9e654149f9ee197a8b2d801c5a80e30e.zip
Avoid assuming that struct varattrib_pointer doesn't get padded by the
compiler --- at least on ARM, it does. I suspect that the varvarlena patch has been creating larger-than-intended toast pointers all along on ARM, but it wasn't exposed until the latest tweak added some Asserts that calculated the expected size in a different way. We could probably have fixed this by adding __attribute__((packed)) as is done for ItemPointerData, but struct varattrib_pointer isn't really all that useful anyway, so it seems cleanest to just get rid of it and have only struct varattrib_1b_e. Per results from buildfarm member quagga.
Diffstat (limited to 'src/backend/executor/nodeResult.c')
0 files changed, 0 insertions, 0 deletions