Re: Maintaining a materialized view only on a replica

From: Craig Ringer <ringerc(at)ringerc(dot)id(dot)au>
To: Herouth Maoz <herouth(at)unicell(dot)co(dot)il>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Maintaining a materialized view only on a replica
Date: 2012-09-04 21:52:49
Message-ID: 50467831.3030703@ringerc.id.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Subject changed to describe the problem. Reply in-line.

On 09/04/2012 07:57 PM, Herouth Maoz wrote:

> The issue is that when an insert or an update is fired, I can't say
> whether all the segments of the same transaction have been written yet,
> and if only some of them were written, there is no guarantee on the
> order in which they are written.

Does Slony-I provide stronger guarantees? If your replication doesn't
guarantee ordering then you're going to have a very hard time doing this.

> Is this
> feasible at all? How would you achieve it?

I'd try to find a replication system that guaranteed ordering if at all
possible.

--
Craig Ringer

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Aram Fingal 2012-09-04 21:59:16 Re: crosstab
Previous Message Gavin Flower 2012-09-04 21:13:09 Re: "Too far out of the mainstream"