public inbox for [email protected]  

help / color / mirror / Atom feed

From: Konstantin Knizhnik <[email protected]>
To: Tomas Vondra <[email protected]>
Cc: 曾文旌(义从) <[email protected]>
Cc: Pavel Stehule <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: PostgreSQL Hackers <[email protected]>
Cc: 蔡松露(子嘉) <[email protected]>
Cc: Cai, Le <[email protected]>
Cc: 萧少聪(铁庵) <[email protected]>
Subject: Re: [Proposal] Global temporary tables
Date: Fri, 10 Jan 2020 15:24:34 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <20200109163037.u76k3kdr3pcmrytb@development>
References: <CA+Tgmob_Fg9PfNjjOReJtAE4B5gc8+UqHh+tztJ_C+iRN4KHSw@mail.gmail.com>
	<[email protected]>
	<CAFj8pRBo8YZ=bJESqf2fkxGL8Bq2Fs7=SjxisS7UhXHh6yPSfA@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<20200105200603.wrb4beacwb57hhpk@development>
	<[email protected]>
	<20200106110119.zfrg2m5e2q5mvi5v@development>
	<[email protected]>
	<20200109163037.u76k3kdr3pcmrytb@development>



On 09.01.2020 19:30, Tomas Vondra wrote:


>
>>
>>>
>>>> 3 Still no one commented on GTT's transaction information 
>>>> processing, they include
>>>> 3.1 Should gtt's frozenxid need to be care?
>>>> 3.2 gtt’s clog clean
>>>> 3.3 How to deal with "too old" gtt data
>>>>
>>>
>>> No idea what to do about this.
>>>
>>
>> I wonder what is the specific of GTT here?
>> The same problem takes place for normal (local) temp tables, doesn't it?
>>
>
> Not sure. TBH I'm not sure I understand what the issue actually is. 

Just open session, create temporary table and insert some data in it.
Then in other session run 2^31 transactions (at my desktop it takes 
about 2 hours).
As far as temp tables are not proceeded by vacuum, database is stalled:

  ERROR:  database is not accepting commands to avoid wraparound data 
loss in database "postgres"

It seems to be quite dubious behavior and it is strange to me that 
nobody complains about it.
We discuss  many issues related with temp tables (statistic, parallel 
queries,...) which seems to be less critical.

But this problem is not specific to GTT - it can be reproduced with 
normal (local) temp tables.
This is why I wonder why do we need to solve it in GTT patch.

-- 
Konstantin Knizhnik
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

view thread (492+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: [Proposal] Global temporary tables
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox