Re: User feedback requested on temp tables usage for Hot Standby - Mailing list pgsql-general

From Ben Chobot
Subject Re: User feedback requested on temp tables usage for Hot Standby
Date
Msg-id 4796FE51-0B5E-418C-B84E-040518FA6FC4@silentmedia.com
Whole thread Raw
In response to User feedback requested on temp tables usage for Hot Standby  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-general
On Oct 27, 2011, at 5:13 PM, Simon Riggs wrote:

> Some people have asked for the ability to create temp tables on a Hot
> Standby server.
>
> I've got a rough implementation plan but it would have some
> restrictions, so I would like to check my understanding of the use
> case for this feature so I don't waste time implementing something
> nobody actually finds useful.
>
> My understanding is that the main use cases for that would be limited
> to these two options only:
>
> 1. CREATE TEMP TABLE foo AS SELECT ....
>
> 2. CREATE TEMP TABLE foo (..);
>    INSERT INTO foo ...
>
> and sometimes a TRUNCATE foo;
>
> In almost all cases people don't run multiple INSERTs, nor do they run
> UPDATEs or DELETEs, so the above actions would cover 99% of use cases.
>
> Can anyone give backup to that opinion, or alternate viewpoints?

The times that we would use a temp table on a slave are times when we would want to materialize a large set of
intermediateresults while doing ad hoc queries. This seems to cover that….. although, just to be sure, do I understand
youin that UDPATEs and DELETEs would not be allowed? That would be fine, but having multiple INSERTs would be very
handy. 

Of course, even having a one-time insert temp table is better than no temp table at all. :)


pgsql-general by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: PostGIS in a commercial project
Next
From: "Stephen Denne"
Date:
Subject: Server move using rsync