From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Gregory Stark <stark(at)enterprisedb(dot)com> |
Cc: | Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [PATCH] Cleanup of GUC units code |
Date: | 2008-09-08 14:32:40 |
Message-ID: | 20080908143240.GD4411@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Gregory Stark wrote:
> "Greg Sabino Mullane" <greg(at)turnstep(dot)com> writes:
>
> > Tom Lane wrote:
> >> My vote is to reject the patch and work on a config checker.
> >
> > +1
> >
> >> postgres=# set work_mem = '1g';
> >> ERROR: invalid value for parameter "work_mem": "1g"
> >
> > Perhaps this would be a great place for a HINT listing all
> > valid inputs, if not there already?
>
> It is, I paraphrased it on my original message as:
>
> HINT: It's perfectly clear what you want but I'm going to refuse to do
> it until you type it exactly as I say: "GB"
It's good as a joke, but what if the user says '1024b'? Does it mean
1024 blocks or one kilobyte? If blocks, what size are we talking, the
usual 512 bytes, or our BLCKSZ?
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
From | Date | Subject | |
---|---|---|---|
Next Message | Gregory Stark | 2008-09-08 14:40:40 | Re: [PATCH] Cleanup of GUC units code |
Previous Message | Gregory Stark | 2008-09-08 14:27:43 | Re: [PATCH] Cleanup of GUC units code |