Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bZEhu-0001Vc-P5 for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Aug 2016 10:01:23 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bZEhu-0002DI-0I for pgsql-hackers@arkaria.postgresql.org; Mon, 15 Aug 2016 10:01:22 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bZEht-0002D2-8T for pgsql-hackers@postgresql.org; Mon, 15 Aug 2016 10:01:21 +0000 Received: from newmail.postgrespro.ru ([93.174.131.138] helo=mail.postgrespro.ru) by makus.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bZEhq-0003Xw-CJ for pgsql-hackers@postgresql.org; Mon, 15 Aug 2016 10:01:20 +0000 Received: from localhost (localhost [127.0.0.1]) by mail.postgrespro.ru (Postfix) with ESMTP id 378F921C2CC4; Mon, 15 Aug 2016 13:01:16 +0300 (MSK) X-Virus-Scanned: Debian amavisd-new at postgrespro.ru Received: from mail.postgrespro.ru ([127.0.0.1]) by localhost (mail.postgrespro.ru [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PdCJBwxtoBFA; Mon, 15 Aug 2016 13:01:16 +0300 (MSK) Received: from e733 (unknown [192.168.27.1]) by mail.postgrespro.ru (Postfix) with ESMTPSA id 0A5BE21C2863; Mon, 15 Aug 2016 13:01:16 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mail; t=1471255276; bh=J+M91V2mJgfNC+mDlExyzY1SFd19i57guMk7FHlqAfg=; h=Date:From:To:Cc:Subject:In-Reply-To:References; b=ConDQapjJDSnOuxm0gedySbe8yUNrnXBDCpVsA7rGhHT3DCusOxTHj7x4W2u9X4+e XRGZGNE8GiELD2vBc6VXgwKT/Y49FbteJICEwcuXdLgpygeStPucaEtp+mtUIYxpHx pMQRsX9FIf5UNxMXaAEK0gXFc3A80IcGpBfhXNto= Date: Mon, 15 Aug 2016 13:00:04 +0300 From: Aleksander Alekseev To: Pavel Stehule Cc: PostgreSQL Hackers , Andres Freund , Tom Lane , Robert Haas , Dmitry Dolgov <9erthalion6@gmail.com>, Tomas Vondra , David Steele Subject: Re: [Patch] Temporary tables that do not bloat pg_catalog (a.k.a fast temp tables) Message-ID: <20160815130004.72effe70@e733> In-Reply-To: References: <20160801124531.66cde374@fujitsu> <26c3bc60-6613-e7ab-517a-53136f01fb6c@2ndquadrant.com> <13191.1470072250@sss.pgh.pa.us> <20160804151451.6fb87507@fujitsu> <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> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: -2.5 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-hackers Precedence: bulk Sender: pgsql-hackers-owner@postgresql.org > But we can change this discussion little bit different. I believe so > solution should be *global temporary tables*. These tables has > persistent catalogue entries. Data are joined with session. These > tables can be effective solution of problem with temporary tables, > can be strong benefit for developers (more comfortable, possible > static analyse of PLpgSQL) and it simplify life to all people who has > do migration from Oracle. So only benefits are there :). I don't think that global temporary tables solve "catalog bloating that causes auto vacuum" problem. I suggest we don't change a topic. Or maybe I don't know something about global temporary tables? -- 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