aboutsummaryrefslogtreecommitdiff
path: root/src/backend/parser/parse_expr.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2010-07-29 19:23:37 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2010-07-29 19:23:37 +0000
commitb08fd11508a2b36e64f456d8e0345f1c66dae333 (patch)
tree05f32934ec1106fbba8c6d4b1761b253d29cbb0d /src/backend/parser/parse_expr.c
parent2d8346182f5cbf743aa2a807893291d74321f8c0 (diff)
downloadpostgresql-b08fd11508a2b36e64f456d8e0345f1c66dae333.tar.gz
postgresql-b08fd11508a2b36e64f456d8e0345f1c66dae333.zip
Fix another longstanding problem in copy_relation_data: it was blithely
assuming that a local char[] array would be aligned on at least a word boundary. There are architectures on which that is pretty much guaranteed to NOT be the case ... and those arches also don't like non-aligned memory accesses, meaning that log_newpage() would crash if it ever got invoked. Even on Intel-ish machines there's a potential for a large performance penalty from doing I/O to an inadequately aligned buffer. So palloc it instead. Backpatch to 8.0 --- 7.4 doesn't have this code.
Diffstat (limited to 'src/backend/parser/parse_expr.c')
0 files changed, 0 insertions, 0 deletions