diff options
| author | Peter Eisentraut <peter_e@gmx.net> | 2016-12-21 12:00:00 -0500 |
|---|---|---|
| committer | Peter Eisentraut <peter_e@gmx.net> | 2016-12-21 09:06:49 -0500 |
| commit | f3b421da5f4addc95812b9db05a24972b8fd9739 (patch) | |
| tree | 89a189a33e6eb712353b5f6397dd728a54d2d9e9 /src/backend/executor/nodeModifyTable.c | |
| parent | ecbdc4c555f43b1ac284c734752b00c2ea6f277b (diff) | |
| download | postgresql-f3b421da5f4addc95812b9db05a24972b8fd9739.tar.gz postgresql-f3b421da5f4addc95812b9db05a24972b8fd9739.zip | |
Reorder pg_sequence columns to avoid alignment issue
On AIX, doubles are aligned at 4 bytes, but int64 is aligned at 8 bytes.
Our code assumes that doubles have alignment that can also be applied to
int64, but that fails in this case. One effect is that
heap_form_tuple() writes tuples in a different layout than
Form_pg_sequence expects.
Rather than rewrite the whole alignment code, work around the issue by
reordering the columns in pg_sequence so that the first int64 column
naturally comes out at an 8-byte boundary.
Diffstat (limited to 'src/backend/executor/nodeModifyTable.c')
0 files changed, 0 insertions, 0 deletions