From: | Bruce Momjian <bruce(at)momjian(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, jd(at)commandprompt(dot)com, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Unsupported effective_io_concurrency platforms |
Date: | 2009-03-28 23:41:32 |
Message-ID: | 200903282341.n2SNfWl11942@momjian.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Peter Eisentraut <peter_e(at)gmx(dot)net> writes:
> > Joshua D. Drake wrote:
> > Do we want to give a more informative error message, like "not supported
> > on this platform?"
>
> > The trick will be to fit this into the GUC framework.
>
> You could do it by enforcing the limit in an assign hook, but I'm
> not convinced it's worth the trouble.
I have created a patch to at least display a more helpful message,
without being specific:
test=> set effective_io_concurrency = 1;
ERROR: parameter "effective_io_concurrency" cannot be changed from 0
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 2.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-03-29 02:29:32 | Re: PQinitSSL broken in some use casesf |
Previous Message | Bruce Momjian | 2009-03-28 22:05:30 | Re: 8.4 release notes proof reading 1/2 |