aboutsummaryrefslogtreecommitdiff
path: root/src/backend/optimizer/util/pathnode.c
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2017-03-31 20:35:51 -0400
committerRobert Haas <rhaas@postgresql.org>2017-03-31 20:47:50 -0400
commit9b6e8d8f86acde571d967f85c8b8ae695a3ddba8 (patch)
tree5be89fcc3eaf40b93b68b78ce47c643d7b418209 /src/backend/optimizer/util/pathnode.c
parentfa0d1fd8955ca22642890421721bcc2de6a54c2b (diff)
downloadpostgresql-9b6e8d8f86acde571d967f85c8b8ae695a3ddba8.tar.gz
postgresql-9b6e8d8f86acde571d967f85c8b8ae695a3ddba8.zip
Don't use bgw_main even to specify in-core bgworker entrypoints.
On EXEC_BACKEND builds, this can fail if ASLR is in use. Backpatch to 9.5. On master, completely remove the bgw_main field completely, since there is no situation in which it is safe for an EXEC_BACKEND build. On 9.6 and 9.5, leave the field intact to avoid breaking things for third-party code that doesn't care about working under EXEC_BACKEND. Prior to 9.5, there are no in-core bgworker entrypoints. Petr Jelinek, reviewed by me. Discussion: http://postgr.es/m/09d8ad33-4287-a09b-a77f-77f8761adb5e@2ndquadrant.com
Diffstat (limited to 'src/backend/optimizer/util/pathnode.c')
0 files changed, 0 insertions, 0 deletions