Re: [HACKERS] proposal: session server side variables - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: [HACKERS] proposal: session server side variables
Date
Msg-id fff92202-3782-0cd0-ee37-70ae490fce55@BlueTreble.com
Whole thread Raw
In response to Re: [HACKERS] proposal: session server side variables  (Fabien COELHO <coelho@cri.ensmp.fr>)
Responses Re: [HACKERS] proposal: session server side variables  (Fabien COELHO <coelho@cri.ensmp.fr>)
List 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)



pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [HACKERS] propose to pushdown qual into EXCEPT
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] Clarifying "server starting" messaging in pg_ctl start without --wait