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

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: pgsql-hackers(at)lists(dot)postgresql(dot)org
Cc: Michael Paquier <michael(at)paquier(dot)xyz>
Subject: Re: Shouldn't current_schema() be at least PARALLEL RESTRICTED?
Date: 2019-03-26 14:16:00
Views: Raw Message | Whole Thread | Download mbox | Resend email
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

In response to


Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2019-03-26 14:21:25 Re: pgsql: Get rid of backtracking in jsonpath_scan.l
Previous Message Tom Lane 2019-03-26 14:03:35 Re: Misleading errors with column references in default expressions and partition bounds