From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Andrew Dunstan <andrew(at)dunslane(dot)net> |
Subject: | Re: Portability issues in shm_mq |
Date: | 2014-03-20 13:35:38 |
Message-ID: | CA+TgmobRpzALc+PBaZATboGOwR3+nrLeL72BZw12R_OSOkGrRw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Mar 18, 2014 at 4:14 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Tue, Mar 18, 2014 at 12:15 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Meh. I think you're putting a bit too much faith in your ability to
>>> predict the locus of bugs that you think aren't there.
>
>> Well, I'm open to suggestions.
>
> As a suggestion: it'd be worth explicitly testing zero-byte and one-byte
> messages, those being obvious edge cases. Then, say, randomly chosen
> lengths in the range 100-1000; this would help ferret out odd-length
> issues. And something with message sizes larger than the queue size.
All right, done. Let's see if that tickles any edge cases we haven't
hit before.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2014-03-20 14:38:39 | Re: Archive recovery won't be completed on some situation. |
Previous Message | Etsuro Fujita | 2014-03-20 12:59:22 | Re: inherit support for foreign tables |