Re: pgsql: Restrict the use of temporary namespace in two-phase transaction

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Date: 2019-01-22 05:17:27
Message-ID: 20190122051727.GB8719@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Jan 22, 2019 at 01:47:05PM +0900, Masahiko Sawada wrote:
> Or can we make the test script set force_parallel_mode = off? Since
> the failure case is a very rare in real world I think that it might be
> better to change the test scripts rather than changing properly of
> current_schema().

Please see 396676b, which is in my opinion a quick workaround to the
problem. Even if that's a rare case, it would be confusing to the
user to see it :(
--
Michael

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Masahiko Sawada 2019-01-22 09:09:08 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Previous Message Masahiko Sawada 2019-01-22 04:47:05 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2019-01-22 05:20:07 Re: Typo: llvm*.cpp files identified as llvm*.c
Previous Message Gavin Flower 2019-01-22 05:13:45 Re: Early WIP/PoC for inlining CTEs