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 intermediate results while doing ad hoc queries. This seems to cover that….. although, just to be sure, do I understand you in 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. :) -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
