Re: including backend ID in relpath of temp rels - updated patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: including backend ID in relpath of temp rels - updated patch
Date
Msg-id AANLkTimu7oSg8wDWfaUxLnL9PTnYGWVwXmOvwzyp=PVR@mail.gmail.com
Whole thread Raw
In response to Re: including backend ID in relpath of temp rels - updated patch  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: including backend ID in relpath of temp rels - updated patch  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Aug 6, 2010 at 3:47 PM, Robert Haas <robertmhaas@gmail.com> wrote:
>>> Do you think it's worth worrying about the reduction in the number of
>>> possible SI message types?
>>
>> IIRC the number of message types is the number of catalog caches plus
>> half a dozen or so.  We're a long way from exhausting even a 1-byte
>> ID field; and we could play more games if we had to, since there would
>> be a padding byte free in the message types that refer to a catalog
>> cache.  IOW, 1-byte id doesn't bother me.
>
> OK.

Here's an updated patch, with the invalidation changes merged in and
hopefully-suitable adjustments elsewhere.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company

Attachment

pgsql-hackers by date:

Previous
From: Fujii Masao
Date:
Subject: Re: RecordTransactionCommit() and SharedInvalidationMessages
Next
From: "Joshua D. Drake"
Date:
Subject: Re: patch: Add JSON datatype to PostgreSQL (GSoC, WIP)