On Wed, May 2, 2012 at 11:39 AM, Michael Nolan <htfoot(at)gmail(dot)com> wrote:
> What is the use case for temporary tables on a hot standby server?
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?"
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2012-05-02 16:06:43|
|Subject: Re: clog double-dip in heap_hot_search_buffer |
|Previous:||From: Michael Nolan||Date: 2012-05-02 15:39:21|
|Subject: Re: Temporary tables under hot standby|