Horton

Re: Shouldn't current_schema() be at least PARALLEL RESTRICTED?

Daniel Gustafsson <daniel@yesql.se>

View thread View on postgr.es
From: Daniel Gustafsson <daniel@yesql.se>
To: pgsql-hackers@lists.postgresql.org
Cc: Michael Paquier <michael@paquier.xyz>
Date: 2019-03-26T14:16:00Z
Lists: pgsql-hackers 
The following review has been posted through the commitfest application:
make installcheck-world:  tested, passed
Implements feature:       tested, passed
Spec compliant:           not tested
Documentation:            not tested

Reviewing the codepath in question (as well as the commit that changed the behaviour of fetch_search_path()), switching current_schema(s) to parallel-unsafe seems like the correct solution. check-world tests pass cleanly and no documentation patch is required.

Switching to ready for committer.

The new status of this patch is: Ready for Committer

Commits

  1. Switch function current_schema[s]() to be parallel-unsafe