aboutsummaryrefslogtreecommitdiff
path: root/contrib/intarray/_int_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2005-11-19 01:50:08 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2005-11-19 01:50:08 +0000
commit1e9a1a70adc1f36d9ba8cd67ce974f777df7aafb (patch)
tree2f254673cf73e55c6f78bc45d6ae4ce25ea307b3 /contrib/intarray/_int_gist.c
parent8685c472235b7a5bcc786f66ba9adde44e3d670c (diff)
downloadpostgresql-1e9a1a70adc1f36d9ba8cd67ce974f777df7aafb.tar.gz
postgresql-1e9a1a70adc1f36d9ba8cd67ce974f777df7aafb.zip
Change array_push and array_cat so that they retain the lower bound of
the array (for array_push) or higher-dimensional array (for array_cat) rather than decrementing it as before. This avoids generating lower bounds other than one for any array operation within the SQL spec. Per recent discussion. Interestingly, this seems to have been the original behavior, because while updating the docs I noticed that a large fraction of relevant examples were *wrong* for the old behavior and are now right. Is it worth correcting this in the back-branch docs?
Diffstat (limited to 'contrib/intarray/_int_gist.c')
0 files changed, 0 insertions, 0 deletions