pg.ddx.io pgsql-hackers@postgresql.org mailing list archive help / color / mirror / Atom feed From: Aleksander Alekseev <a.alekseev@postgrespro.ru>
To: Pavel Stehule <pavel.stehule@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Andres Freund <andres@anarazel.de>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: Dmitry Dolgov <9erthalion6@gmail.com>
Cc: Tomas Vondra <tomas.vondra@2ndquadrant.com>
Cc: David Steele <david@pgmasters.net>
Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)
Date: Mon, 15 Aug 2016 13:18:38 +0300
Message-ID: <20160815131838.592c5667@e733> (raw )
In-Reply-To: <CAFj8pRCRhxZ8MGJ58yahP=dtmEnupaiXOk+CwCVmip8VyK8yjQ@mail.gmail.com >
References: <20160801124531.66cde374@fujitsu >
<26c3bc60-6613-e7ab-517a-53136f01fb6c@2ndquadrant.com >
<13191.1470072250@sss.pgh.pa.us >
<20160804151451.6fb87507@fujitsu >
<CA+Tgmob+AS4vPA-wp+KevL7q+qK4c7yZ5wjGvEv6EqPChE2oYQ@mail.gmail.com >
<CA+q6zcVLO7VoHHpRn9ExkiWksF6TwJ-rabqgwRJgC2_ci8_UEQ@mail.gmail.com >
<CA+TgmoYstEXxa0KCAPVAVseTwBpb51t=bK1FBU8L8h4sC3XWBQ@mail.gmail.com >
<14212.1470595566@sss.pgh.pa.us >
<20160815005755.gswdyjfob7dzw4yp@alap3.anarazel.de >
<20319.1471223097@sss.pgh.pa.us >
<20160815010852.5ijua2wm2edzimd4@alap3.anarazel.de >
<20160815120136.6f9c8dd1@e733 >
<CAFj8pRBhsma3YFrTevm1_wvo5V6UbJUj3R1Fbaqni29suVhiHg@mail.gmail.com >
<20160815130004.72effe70@e733 >
<CAFj8pRCRhxZ8MGJ58yahP=dtmEnupaiXOk+CwCVmip8VyK8yjQ@mail.gmail.com >
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>
> The global temporary tables has persistent rows in the catalogue. The
> mapping to files can be marked as special and real mapping should be
> only in memory.
>
> So the changes in catalogue related to global temporary tables are
> pretty less frequently.
I'm afraid I still don't get it. Let say I have an application that
does `CREATE TEMP TABLE xx ; DROP TABLE xx` in every session all the
time. Naturally there is not only one temp table per session. Could you
explain please in more detail how exactly do these persistent rows help?
--
Best regards,
Aleksander Alekseev
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
view thread (63+ messages) latest in thread
Message-ID: <20160815131838.592c5667@e733>
Permalink: ../20160815131838.592c5667@e733/
Also on: postgresql.org/message-id/20160815131838.592c5667@e733
copy link · copy postgr.es
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: pgsql-hackers@postgresql.org
Cc: a.alekseev@postgrespro.ru, pavel.stehule@gmail.com, andres@anarazel.de, tgl@sss.pgh.pa.us, robertmhaas@gmail.com, 9erthalion6@gmail.com, tomas.vondra@2ndquadrant.com, david@pgmasters.net
Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables)
In-Reply-To: <20160815131838.592c5667@e733>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox