From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
---|---|
To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Temp tables, pg_class_temp and AccessExclusiveLocks |
Date: | 2014-11-01 19:32:15 |
Message-ID: | CAFj8pRCdFJ4OnKyP90OgBxz40W=GcTXSaAwU_F+dC8LyT5v5Ng@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi
good idea. Mix of these both strategies can be a base for global temp
tables implementation.
Pavel
2014-10-31 15:53 GMT+01:00 Simon Riggs <simon(at)2ndquadrant(dot)com>:
> While investigating how to reduce logging of AccessExclusiveLocks for
> temp tables, I came up with the attached patch.
>
> My feeling was "that's an ugly patch", but it set me thinking that a
> more specialised code path around temp tables could be useful in other
> ways, and therefore worth pursuing further.
>
> The patch creates a relation_open_temp(), which could then allow a
> RelationIdGetTempRelation() which could have a path that calls
> ScanPgRelation on a new catalog table called pg_class_temp, and other
> _temp catalog table accesses.
>
> So we could isolate all temp table access to specific tables. That would
> * cause less bloat in the main catalog tables
> * avoid logging AccessExclusiveLocks on temp tables
> * less WAL traffic
>
> Why less WAL traffic? Because we can choose then to make *_temp catalog
> tables
> 1. use unlogged table mechanism
> 2. use local tables inside the local buffer manager
>
> My preference would be (1) because all we need to do is change the
> catalog table oid when searching, we don't need to do anything else.
>
> --
> Simon Riggs http://www.2ndQuadrant.com/
> PostgreSQL Development, 24x7 Support, Training & Services
>
>
> --
> Sent via pgsql-hackers mailing list (pgsql-hackers(at)postgresql(dot)org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-hackers
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-11-01 19:33:27 | Re: Let's drop two obsolete features which are bear-traps for novices |
Previous Message | Andres Freund | 2014-11-01 19:17:14 | Re: Let's drop two obsolete features which are bear-traps for novices |