aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/gist/gist.c
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2019-03-27 11:35:12 +0900
committerMichael Paquier <michael@paquier.xyz>2019-03-27 11:35:12 +0900
commit5bde1651bbba9984dc32bbeb68b329cfd3f92767 (patch)
treeac60dfcd85414fc5b720f8dd48f96d3ed9efbbbb /src/backend/access/gist/gist.c
parent6ca015f9f073eef40f933f587e0b166b87261406 (diff)
downloadpostgresql-5bde1651bbba9984dc32bbeb68b329cfd3f92767.tar.gz
postgresql-5bde1651bbba9984dc32bbeb68b329cfd3f92767.zip
Switch function current_schema[s]() to be parallel-unsafe
When invoked for the first time in a session, current_schema() and current_schemas() can finish by creating a temporary schema. Currently those functions are parallel-safe, however if for a reason or another they get launched across multiple parallel workers, they would fail when attempting to create a temporary schema as temporary contexts are not supported in this case. The original issue has been spotted by buildfarm members crake and lapwing, after commit c5660e0 has introduced the first regression tests based on current_schema() in the tree. After that, 396676b has introduced a workaround to avoid parallel plans but that was not completely right either. Catversion is bumped. Author: Michael Paquier Reviewed-by: Daniel Gustafsson Discussion: https://postgr.es/m/20190118024618.GF1883@paquier.xyz
Diffstat (limited to 'src/backend/access/gist/gist.c')
0 files changed, 0 insertions, 0 deletions