Re: Synchronous replication + pgPool: not all transactions immediately visible on standby

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Tatsuo Ishii <ishii(at)postgresql(dot)org>
Cc: spam_eater(at)gmx(dot)net, PostgreSQL mailing lists <pgsql-general(at)postgresql(dot)org>
Subject: Re: Synchronous replication + pgPool: not all transactions immediately visible on standby
Date: 2014-09-25 12:10:26
Message-ID: CAB7nPqTMdAzv2sYYoOT_a11-7r0Ei4HGAKG5KXnLDJdkkng0gA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Thu, Sep 25, 2014 at 8:40 AM, Tatsuo Ishii <ishii(at)postgresql(dot)org> wrote:
> Postgres-XC (or Postgres-XL which is a fork of Postgres-XC) overcomes
> the issue by using "global transaction management" technique.
... At the cost of reducing data availability for sharded tables, and
increasing write load for replicated tables, both things not that cool
for data warehouse applications, better for OLTP loads.
Regards,
--
Michael

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2014-09-25 13:13:40 Re: How to clone CURRENT_DATE to SYSDATE ?
Previous Message Roopeshakumar Narayansa Shalgar (rshalgar) 2014-09-25 10:44:42 PANIC: could not create file "pg_xlog/xlogtemp.7884": No space left on device