Marc G. Fournier wrote: > > > On Sat, 8 Nov 2003, Tom Lane wrote: > > > <[EMAIL PROTECTED]> writes: > > > select * from information_schema.tables; > > > ERROR: unrecognized privilege type: "RERERENCES" > > > > > Replacing the word "RERERENCES" with "REFERENCES" in > > > the predicate "has_table_privilege(c.oid, > > > 'RERERENCES'::text)" near the end of the view SQL > > > seems to correct the problem. > > > > Good catch. There are two other places with the same typo :-( (all > > copied and pasted no doubt). > > > > I've applied the patch but am loathe to force an initdb this late in > > the beta cycle. Any opinions out there? > > Annoying as a spelling mistake is (and, from my read of the above, that is > all it is?), I don't thnk it warrants forcing an initdb ... unless I'm > missing a larger scope?
It must have a larger affect than just a spelling effect if he is seeing an error: > > ERROR: unrecognized privilege type: "RERERENCES" I now see the question Tom had was wether we force an initdb. Seems this query "select * from information_schema.tables;" is broken without it. I think we should fix it but not force an initdb --- information_schema is new and I am not sure how many people are using it. -- Bruce Momjian | http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square, Pennsylvania 19073 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
