| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Daniel Farina <daniel(at)heroku(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Subject: | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Date: | 2012-06-20 17:51:02 |
| Message-ID: | CA+U5nMKJsvWst3cxGsK5n6YTEFrzNRczG8U_AXdgabZDpoUTdQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 June 2012 01:40, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> I think extraction is a very sensible place to start; actually, I
>> think it's the best possible place to start. But this particular
>> thread is about adding origin_ids to WAL, which I think is definitely
>> not the best place to start.
> Yep. I think the reason everyone started at it is that the patch was actually
> really simple ;).
> Note that the wal enrichement & decoding patches were before the origin_id
> patch in the patchseries ;)
Actually, I thought it would be non contentious...
A format change, so early in release cycle. Already openly discussed
with no comment. Using wasted space for efficiency, for information
already in use by Slony for similar reasons.
Oh well.
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-06-20 17:52:59 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Previous Message | Robert Haas | 2012-06-20 17:50:37 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |