diff options
| author | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-01-19 10:15:08 -0300 |
|---|---|---|
| committer | Alvaro Herrera <alvherre@alvh.no-ip.org> | 2018-01-19 10:17:54 -0300 |
| commit | 1ef61ddce9086c30a18a6ecc48bc3ce0ef62cb39 (patch) | |
| tree | 540975b00c80b29ec6ad9a756e597da92395c073 /src/backend/utils/adt/amutils.c | |
| parent | 29d58fd3adae9057c3fd502393b2f131bc96eaf9 (diff) | |
| download | postgresql-1ef61ddce9086c30a18a6ecc48bc3ce0ef62cb39.tar.gz postgresql-1ef61ddce9086c30a18a6ecc48bc3ce0ef62cb39.zip | |
Fix StoreCatalogInheritance1 to use 32bit inhseqno
For no apparent reason, this function was using a 16bit-wide inhseqno
value, rather than the correct 32 bit width which is what is stored in
the pg_inherits catalog. This becomes evident if you try to create a
table with more than 65535 parents, because this error appears:
ERROR: duplicate key value violates unique constraint «pg_inherits_relid_seqno_index»
DETAIL: Key (inhrelid, inhseqno)=(329371, 0) already exists.
Needless to say, having so many parents is an uncommon situations, which
explains why this error has never been reported despite being having
been introduced with the Postgres95 1.01 sources in commit d31084e9d111:
https://git.postgresql.org/gitweb/?p=postgresql.git;a=blob;f=src/backend/commands/creatinh.c;hb=d31084e9d111#l349
Backpatch all the way back.
David Rowley noticed this while reviewing a patch of mine.
Discussion: https://postgr.es/m/CAKJS1f8Dn7swSEhOWwzZzssW7747YB=2Hi+T7uGud40dur69-g@mail.gmail.com
Diffstat (limited to 'src/backend/utils/adt/amutils.c')
0 files changed, 0 insertions, 0 deletions