> What is the use case for temporary tables on a hot standby server?
> Perhaps this is a noobie question, but it seems to me that a hot standby
> server's use by* applications* or *users* should be limited to transactions
> that don't alter the database in any form.
A very common use for asynchronous replicas is to offload long-running
reporting jobs onto the replica so that they don't bog down the master.
However, long-running reporting jobs often require temporary tables,
especially if they use some 3rd-party vendor's reporting tool. For
example, the average Microstrategy report involves between 1 and 12
PostgreSQL Experts Inc.
In response to
pgsql-hackers by date
|Next:||From: Josh Berkus||Date: 2012-05-03 01:01:38|
|Subject: Re: patch submission: truncate trailing nulls from heap
rows to reduce the size of the null bitmap|
|Previous:||From: Robert Haas||Date: 2012-05-03 00:41:29|
|Subject: Re: Latch for the WAL writer - further reducing idle wake-ups.|