| From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
| Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, andres(at)2ndquadrant(dot)com, robertmhaas(at)gmail(dot)com, daniel(at)heroku(dot)com, pgsql-hackers(at)postgresql(dot)org, 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 19:27:47 |
| Message-ID: | CA+U5nMJ34RWxq6+DuPW8N3O=HB8K_wX38xtR8TGB6FeZo9h57g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 21 June 2012 03:23, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)com> wrote:
>> And then we just put the originid on each heap record for MMR, in some
>> manner, discussed later.
>
>
> I reserve the right to object to that, too :-).
OK. But that would be only for MMR, using special record types.
> Others raised the concern
> that a 16-bit integer is not a very intuitive identifier.
Of course
> Also, as
> discussed, for more complex scenarios just the originid is not sufficient.
> ISTM that we need more flexibility.
Of course
--
Simon Riggs http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2012-06-20 19:27:53 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |
| Previous Message | Simon Riggs | 2012-06-20 19:24:58 | Re: [PATCH 10/16] Introduce the concept that wal has a 'origin' node |