aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2014-08-28 18:21:05 -0400
committerTom Lane <tgl@sss.pgh.pa.us>2014-08-28 18:21:05 -0400
commit7f7eec89b66947e4098773cf286653b9c4f01c88 (patch)
tree8c615dc7701ab77b948be46a7c76e9cdd6fe0619 /src/backend/access/gist/gist.c
parent9df492664a74a948c87232f523eea637920a516b (diff)
downloadpostgresql-7f7eec89b66947e4098773cf286653b9c4f01c88.tar.gz
postgresql-7f7eec89b66947e4098773cf286653b9c4f01c88.zip
Fix citext upgrade script for disallowance of oidvector element assignment.
In commit 45e02e3232ac7cc5ffe36f7986159b5e0b1f6fdc, we intentionally disallowed updates on individual elements of oidvector columns. While that still seems like a sane idea in the abstract, we (I) forgot that citext's "upgrade from unpackaged" script did in fact perform exactly such updates, in order to fix the problem that citext indexes should have a collation but would not in databases dumped or upgraded from pre-9.1 installations. Even if we wanted to add casts to allow such updates, there's no practical way to do so in the back branches, so the only real alternative is to make citext's kluge even klugier. In this patch, I cast the oidvector to text, fix its contents with regexp_replace, and cast back to oidvector. (Ugh!) Since the aforementioned commit went into all active branches, we have to fix this in all branches that contain the now-broken update script. Per report from Eric Malm.
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions