From: | ITAGAKI Takahiro <itagaki(dot)takahiro(at)oss(dot)ntt(dot)co(dot)jp> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers(at)postgreSQL(dot)org |
Subject: | Re: note about syntax for fillfactor patch |
Date: | 2006-07-03 01:03:53 |
Message-ID: | 20060703092340.5661.ITAGAKI.TAKAHIRO@oss.ntt.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I propose that we change the syntax to be
>
> WITH OIDS
> | WITHOUT OIDS
> | WITH (definition)
> | /*EMPTY*/
>
> and say that if you want to specify both OIDS and another option you
> have to write "oids" or "oids=false" in the definition list.
Yeah, it sounds good. However, the syntax "oids=false" is not available
for a limitation of the current parser; it can recognize only numerics or
strings as a value. So oids=0/1 or oids='false'/'true' are ok, but
false/true literals are syntax error.
# CREATE TABLE test1 (i int) WITH (oids=0);
CREATE TABLE
# CREATE TABLE test2 (i int) WITH (oids=false);
ERROR: syntax error at or near "false"
LINE 1: CREATE TABLE test2 (i int) WITH (oids=false);
^
# CREATE TABLE test3 (i int) with (oids='false');
ERROR: oids requires a boolean value
(*) We can resolve this by adding a T_String handler to defGetBoolean().
Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center
From | Date | Subject | |
---|---|---|---|
Next Message | ITAGAKI Takahiro | 2006-07-03 01:56:02 | Re: table/index fillfactor control, try 3 |
Previous Message | Andrew Dunstan | 2006-07-03 00:08:19 | Re: odd 7.4 build failure on new sparc machine |