Re: Portability issues in shm_mq - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Portability issues in shm_mq
Date
Msg-id CA+TgmoaW=RSPM-dpj_m7PtvCZiQUkkq9huvzw31MM4h061HP1Q@mail.gmail.com
Whole thread Raw
In response to Re: Portability issues in shm_mq  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Portability issues in shm_mq  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Mon, Mar 17, 2014 at 1:26 PM, Robert Haas <robertmhaas@gmail.com> wrote:
> Oh, yeah.  Duh.  Clearly my brain isn't working today.  Hmm, so maybe
> this will be fairly simple... will try it out.

OK, I tried this out.  The major complication that cropped up was
that, if we make the length word always a Size but align the buffer to
MAXIMUM_ALIGNOF, then the length word might get split if sizeof(Size)
> MAXIMUM_ALIGNOF.  That doesn't look too bad, but required changing a
couple of if statements into while loops, and changing around the
structure of a shm_mq_handle a bit.  See attached.

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

Attachment

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: Minimum supported version of Python?
Next
From: David Johnston
Date:
Subject: Re: Minimum supported version of Python?