Postgres Pro
Downloads
Home   >   mailing lists

Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node - Mailing list pgsql-hackers

From Kevin Grittner
Subject Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node
Date
Msg-id 4FE0B6840200002500048725@gw.wicourts.gov
Whole thread Raw
In response to Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
List pgsql-hackers
Tree view 
Andres Freund <andres@2ndquadrant.com> wrote:
> Yes, thats definitely a valid use-case. But that doesn't preclude
> the other - also not uncommon - use-case where you want to have
> different master which all contain up2date data.
I agree.  I was just saying that while one requires an origin_id,
the other doesn't.  And those not doing MM replication definitely
don't need it.
-Kevin

pgsql-hackers by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: WAL format changes
Next
From: Andres Freund
Date:
Subject: Re: WAL format changes