On Fri, May 27, 2011 at 1:53 AM, Jaime Casanova wrote:
> btw, i guess we should be defaulting to asynchronous standbys (ie:
> synchronous_commit=local)
By default, synchronous_standby_names is empty, which makes
synchronous_commit=on equivalent to synchronous_commit=local. So I
think the current
On Fri, May 27, 2011 at 7:15 AM, Tomonari Katsumata
wrote:
> I've thought that if there are no standby,
> the primary would behave like stand-alone...
> sorry, this is my misunderstanding.
It is a common misunderstanding. The programmed behaviour leads to the
most trusted level of robustness.
-
Hi, Jaime
thank you for your answer.
I understand it.
I turned synchronous_commit to "local",
I get desirable behavior.
I've thought that if there are no standby,
the primary would behave like stand-alone...
sorry, this is my misunderstanding.
regards,
(2011/05/27 14:53), Jaime Casanova wrot
On Fri, May 27, 2011 at 12:26 AM, Tomonari Katsumata
wrote:
>
>
> I've checked "unlogged table" and "Streaming Replication".
> I'm thinking about using unlogged tables as work-tables on Primary.
>
> 1) construct Streaming Replication Environment.
> Primary and Standby are same server with differe
The following bug has been logged online:
Bug reference: 6042
Logged by: Tomonari Katsumata
Email address: katsumata.tomon...@po.ntts.co.jp
PostgreSQL version: 9.1beta1
Operating system: RHEL5.3 x86_64
Description:unlogged table with Streaming Replication
Details:
H
