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

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: pgsql-committers(at)lists(dot)postgresql(dot)org
Subject: Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Date: 2019-02-11 09:59:20
Message-ID: 5ea2c610-5fb1-4ae2-b48c-b097c680b38f@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On 09/02/2019 16:06, Peter Eisentraut wrote:
> On 08/02/2019 11:00, Michael Paquier wrote:
>> On Fri, Feb 08, 2019 at 10:41:59AM +0100, Peter Eisentraut wrote:
>>> We usually don't use "namespace" in user-facing error messages. Can you
>>> change it to say "temporary schema"?
>>
>> Or just switch to "temporary objects" like it's done on HEAD for the
>> second message?
>
> Yeah, even better.

Committed that way.

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Michael Paquier 2019-02-11 10:55:00 Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
Previous Message Peter Eisentraut 2019-02-11 09:58:26 pgsql: Adjust error message

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Sharma 2019-02-11 10:09:03 Re: ON SELECT rule on a table without columns
Previous Message Michael Meskes 2019-02-11 09:58:04 Re: [PROPOSAL]a new data type 'bytea' for ECPG