Re: Unsupported effective_io_concurrency platforms

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: jd(at)commandprompt(dot)com, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unsupported effective_io_concurrency platforms
Date: 2009-03-25 14:02:43
Message-ID: 23143.1237989763@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2009-03-25 14:38:45 Re: improving concurrent transactin commit rate
Previous Message Kevin Grittner 2009-03-25 13:59:01 Re: New trigger option of pg_standby