Re: pgsql: Restrict the use of temporary namespace in two-phase transaction
От | Masahiko Sawada |
---|---|
Тема | Re: pgsql: Restrict the use of temporary namespace in two-phase transaction |
Дата | |
Msg-id | CAD21AoCwHoZK8VP2q8W2htO_w6SH1m1MtEijGN-PFq8KX5dgUg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: pgsql: Restrict the use of temporary namespace in two-phase transaction (Robert Haas <robertmhaas@gmail.com>) |
Ответы |
Re: pgsql: Restrict the use of temporary namespace in two-phasetransaction
|
Список | pgsql-hackers |
On Sat, Jan 19, 2019 at 5:05 AM Robert Haas <robertmhaas@gmail.com> wrote: > > On Thu, Jan 17, 2019 at 8:08 PM Tom Lane <tgl@sss.pgh.pa.us> wrote: > > > Anyway, it seems to me that this is pointing out to another issue: > > > current_schema() can trigger a namespace creation, hence shouldn't we > > > mark it as PARALLEL UNSAFE and make sure that we never run into this > > > problem? > > > > That seems a bit annoying, but maybe we have little choice? > > The only other option I see is to make current_schema() not trigger a > namespace creation. > 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(). Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: