Re: dsm use of uint64

From: Noah Misch <noah(at)leadboat(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: dsm use of uint64
Date: 2013-10-28 03:34:47
Message-ID: 20131028033447.GA577409@tornado.leadboat.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Oct 25, 2013 at 10:11:41PM -0400, Robert Haas wrote:
> When I wrote the dynamic shared memory patch, I used uint64 everywhere
> to measure sizes - rather than, as we do for the main shared memory
> segment, Size. This now seems to me to have been the wrong decision;
> I'm finding that it's advantageous to make dynamic shared memory
> behave as much like the main shared memory segment as is reasonably
> possible, and using Size facilitates the use of MAXALIGN(),
> TYPEALIGN(), etc. as well as things like add_size() and mul_size()
> which are just as relevant in the dynamic shared memory case as they
> are for the main shared memory segment.
>
> Therefore, I propose to apply the attached patch.

+1. The simplicity of platform-independent type sizing had some attraction,
but not so much to justify this sort of friction with the rest of the system.

--
Noah Misch
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Naoya Anzai 2013-10-28 05:26:58 PostgreSQL Service on Windows does not start. ~ "is not a valid Win32 application"
Previous Message Craig Ringer 2013-10-28 01:51:00 Re: CLUSTER FREEZE