Re: Temporary tables under hot standby - Mailing list pgsql-hackers

From Christopher Browne
Subject Re: Temporary tables under hot standby
Date
Msg-id CAFNqd5UMv5WLq_n4Ru_UgDBn0gpX3c4KVURJ1UtaE0JftJpD6g@mail.gmail.com
Whole thread Raw
In response to Re: Temporary tables under hot standby  (Michael Nolan <htfoot@gmail.com>)
List pgsql-hackers
On Wed, May 2, 2012 at 11:39 AM, Michael Nolan <htfoot@gmail.com> wrote:
> What is the use case for temporary tables on a hot standby server?

Simple...

We required a "hot standby" server in order to get improved reliability.

But we don't want it to sit there chewing power + money, unused.

We want to *use* it to support our reporting applications.

And the developers used temporary tables to marshal results used in
some of those reports.

There are conflicting senses of "read-only" here... - In one strict sense, to generate tuples in temp tables means
it's
not "read only" access. - But since the users running reports aren't allowed to modify the
data in the application tables that they are querying, how is that
*not* fairly characterized as "read only" access???
-- 
When confronted by a difficult problem, solve it by reducing it to the
question, "How would the Lone Ranger handle this?"


pgsql-hackers by date:

Previous
From: Michael Nolan
Date:
Subject: Re: Temporary tables under hot standby
Next
From: Tom Lane
Date:
Subject: Re: clog double-dip in heap_hot_search_buffer