From: | Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com> |
---|---|
To: | Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: proposal: session server side variables |
Date: | 2016-12-24 00:10:14 |
Message-ID: | fff92202-3782-0cd0-ee37-70ae490fce55@BlueTreble.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/23/16 4:24 PM, Fabien COELHO wrote:
> I think that a special purpose variable infrastructure implied by your
> remark is just starting from the end point. The first three points seem
> relevant too because they help focus on other issues.
If you want to ignore performance, there are things you can do with
non-transactional variables that are simply not possible with tables.
But even ignoring that, the performance cost of temp tables is massive
compared to variables. Not only is the access far more complex, but
bloating is a major problem (both in the table itself as well as in the
catalog). That's part of the driver for all the discussion about things
like permanent temp tables (which still leaves a bloat and performance
problem in the table itself).
--
Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX
Experts in Analytics, Data Architecture and PostgreSQL
Data in Trouble? Get it in Treble! http://BlueTreble.com
855-TREBLE2 (855-873-2532)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-12-24 00:10:31 | Re: Clarifying "server starting" messaging in pg_ctl start without --wait |
Previous Message | Tom Lane | 2016-12-24 00:08:10 | Re: propose to pushdown qual into EXCEPT |