From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: More schema queries |
Date: | 2002-05-21 00:00:13 |
Message-ID: | 16323.1021939213@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> writes:
> I'm confused. Does the standalone backend not deal with schemas fully
> and is silently failing 'cos there's nothing technically wrong with the
> pg_catalog.viewname syntax?
The standalone backend does schemas just fine. What is supposed to
ensure that the views get created in pg_catalog is the bit in initdb:
PGSQL_OPT="$PGSQL_OPT -O --search_path=pg_catalog"
The -- parameter should do the equivalent of
SET search_path = pg_catalog;
but apparently it's not working for you; if it weren't there then the
views would indeed get created in public.
Any idea why it's not working?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Manuel Sugawara | 2002-05-21 00:08:07 | Re: Redhat 7.3 time manipulation bug |
Previous Message | Bruce Momjian | 2002-05-20 22:45:59 | I am online today |