From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, fgp(at)phlo(dot)org, gsstark(at)mit(dot)edu, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: beta3 & the open items list |
Date: | 2010-06-20 21:44:42 |
Message-ID: | AANLkTinaict_djj-UDTaf0YKOyEfPBXyL-Ms_Vf9UfpC@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sun, Jun 20, 2010 at 5:32 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>> On Sun, Jun 20, 2010 at 11:36 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Right, of course. That's already in the pending patch isn't it?
>
>> Is this sarcasm, or is there a pending patch I'm not aware of?
>
> https://commitfest.postgresql.org/action/patch_view?id=281
+1 for applying something along these lines, but we'll also need to
update walreceiver to actually use one or more of these new
parameters.
On a quick read, I think I see a problem with this: if a parameter is
specified with a non-zero value and there is no OS support available
for that parameter, it's an error. Presumably, for our purposes here,
we'd prefer to simply ignore any parameters for which OS support is
not available. Given the nature of these parameters, one might argue
that's a more useful behavior in general.
Also, what about Windows?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise Postgres Company
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2010-06-20 21:52:17 | Re: beta3 & the open items list |
Previous Message | Florian Pflug | 2010-06-20 21:41:48 | Re: beta3 & the open items list |