Re: [Proposal] Global temporary tables

From: 曾文旌(义从) <wenjing(dot)zwj(at)alibaba-inc(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>
Cc: "Prabhat Sahu" <prabhat(dot)sahu(at)enterprisedb(dot)com>, "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com>, "Tomas Vondra" <tomas(dot)vondra(at)2ndquadrant(dot)com>, "Konstantin Knizhnik" <k(dot)knizhnik(at)postgrespro(dot)ru>, "PostgreSQL Hackers" <pgsql-hackers(at)postgresql(dot)org>, 蔡松露(子嘉) <zijia(at)taobao(dot)com>, Cai, Le <le(dot)cai(at)alibaba-inc(dot)com>, 萧少聪(铁庵) <shaocong(dot)xsc(at)alibaba-inc(dot)com>
Subject: Re: [Proposal] Global temporary tables
Date: 2020-03-06 07:10:52
Message-ID: 48FC01A4-D680-49FE-8E13-AB09A4E4F1D1@alibaba-inc.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> 2020年3月5日 下午10:38,Robert Haas <robertmhaas(at)gmail(dot)com> 写道:
>
> On Thu, Mar 5, 2020 at 9:19 AM tushar <tushar(dot)ahuja(at)enterprisedb(dot)com> wrote:
>> WARNING: relfilenode 13589/1663/19063 not exist in gtt shared hash when forget
>> ERROR: out of shared memory
>> HINT: You might need to increase max_active_gtt.
>>
>> also , would be great if we can make this error message user friendly like - "max connection reached" rather than memory error
>
> That would be nice, but the bigger problem is that the WARNING there
> looks totally unacceptable. It's looks like it's complaining of some
> internal issue (i.e. a bug or corruption) and the grammar is poor,
> too.

Yes, WARNING should not exist.
This is a bug in the rollback process and I have fixed it in global_temporary_table_v17-pg13.patch

Wenjing

>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message keisuke kuroda 2020-03-06 07:20:21 Re: Exposure related to GUC value of ssl_passphrase_command
Previous Message 曾文旌 (义从) 2020-03-06 07:08:30 Re: [Proposal] Global temporary tables