| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
| Cc: | Andres Freund <andres(at)2ndquadrant(dot)com>, "Baker, Keith [OCDUS Non-J&J]" <KBaker9(at)its(dot)jnj(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal to add a QNX 6.5 port to PostgreSQL |
| Date: | 2014-07-29 00:13:30 |
| Message-ID: | CAM3SWZT_yzE5PE50r9GTrwh7dnM5LXXJmMFfOcvJO9Hh9oZRSw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jul 28, 2014 at 9:41 AM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:
>> I don't think a buildfarm animal that doesn't run the actual upstream
>> code is a good idea. That'll make it a lot harder to understand what's
>> going on when something breaks after a commit. It'd also require the
>> custom patches being rebased ontop of $branch before every run...
>
> hm. oh well. maybe if there was a separate page for custom builds
> (basically, an unsupported section).
I think that's a bad idea. The QNX OS seems to be mostly used in
safety-critical systems; it has a microkernel design. I think it would
be particularly bad to have iffy support for something like that.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Wim Lewis | 2014-07-29 00:14:18 | Re: B-Tree support function number 3 (strxfrm() optimization) |
| Previous Message | Peter Geoghegan | 2014-07-28 23:57:56 | Re: B-Tree support function number 3 (strxfrm() optimization) |