Re: More schema queries - Mailing list pgsql-hackers

From Tom Lane
Subject Re: More schema queries
Date
Msg-id 16323.1021939213@sss.pgh.pa.us
Whole thread Raw
In response to Re: More schema queries  ("Dave Page" <dpage@vale-housing.co.uk>)
List pgsql-hackers
"Dave Page" <dpage@vale-housing.co.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 ofSET 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


pgsql-hackers by date:

Previous
From: "Rich Elwyn"
Date:
Subject: JDBC with SSL for postgresql
Next
From: Tom Lane
Date:
Subject: Re: Language-specific initialization actions