| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Steve Singer <steve(at)ssinger(dot)info> |
| Subject: | Re: Replication Node Identifiers and crashsafe Apply Progress |
| Date: | 2013-11-21 13:22:05 |
| Message-ID: | CA+TgmoZWjfqdrDYTDH=oU0yh+mOuqiv3GORtraQrPPft79_Ykg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Nov 21, 2013 at 6:15 AM, Andres Freund <andres(at)2ndquadrant(dot)com> wrote:
>> > WRT performance: I agree that fixed-width identifiers are more
>> > performant, that's why I went for them, but I am not sure it's that
>> > important. The performance sensitive parts should all be done using the
>> > internal id the identifier maps to, not the public one.
>>
>> But I thought the internal identifier was exactly what we're creating.
>
> Sure. But how often are we a) going to create such an identifier b)
> looking it up?
Never. Make that the replication solution's problem. Make the core
support deal only with UUIDs or pairs of 64-bit integers or something
like that, and let the replication solution decide what they mean.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2013-11-21 13:26:02 | Re: Replication Node Identifiers and crashsafe Apply Progress |
| Previous Message | Craig Ringer | 2013-11-21 13:15:28 | WIP patch for updatable security barrier views |