pgsql: Enforce non-parallel plan when calling current_schema() in newly

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: pgsql: Enforce non-parallel plan when calling current_schema() in newly
Date: 2019-01-18 01:52:48
Message-ID: E1gkJKy-0002mi-8M@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Enforce non-parallel plan when calling current_schema() in newly-added test

current_schema() gets called in the recently-added regression test from
c5660e0, and can be used in a parallel context, causing its call to fail
when creating a temporary schema.

Per buildfarm members crake and lapwing.

Discussion: https://postgr.es/m/20190118005949.GD1883@paquier.xyz

Branch
------
REL_10_STABLE

Details
-------
https://git.postgresql.org/pg/commitdiff/08b53281f4444efb2d5bcc44d6293b05d1aa1335

Modified Files
--------------
src/test/regress/expected/temp.out | 5 ++++-
src/test/regress/sql/temp.sql | 5 ++++-
2 files changed, 8 insertions(+), 2 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2019-01-18 04:55:00 pgsql: Fix incorrect relation name in comment of vacuumlazy.c
Previous Message Tom Lane 2019-01-18 01:08:07 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction