Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)

From: Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
To: Andres Freund <andres(at)anarazel(dot)de>
Cc: Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, Vik Fearing <vik(at)2ndquadrant(dot)fr>, Robert Haas <robertmhaas(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Aleksander Alekseev <a(dot)alekseev(at)postgrespro(dot)ru>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)
Date: 2016-08-31 22:31:44
Message-ID: CADkLM=dyyWBcBKPWAG+Jk3RLvveO8rEJ8A3JO-_1uX5Swgn2RA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Aug 31, 2016 at 6:07 PM, Andres Freund <andres(at)anarazel(dot)de> wrote:

>
> In my experience pg attribute is usually the worst affected. Many tech
> takes won't even have stays entries...
>
>
Mine too. One database currently has a 400GB pg_attribute table, because we
chew through temp tables like popcorn.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jeff Janes 2016-08-31 22:59:02 Re: Notice lock waits
Previous Message Peter Geoghegan 2016-08-31 22:15:16 Re: _mdfd_getseg can be expensive