From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: Operators and schemas |
Date: | 2002-04-16 02:02:10 |
Message-ID: | Pine.LNX.4.30.0204152154190.834-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane writes:
> What I'm now envisioning is that pg_dump will explicitly set
> set search_path = 'foo';
> when dumping or reloading schema foo.
I had imagined that pg_dump would emit commands such as this:
CREATE SCHEMA foo
CREATE TABLE bar ( ... )
CREATE otherthings
;
which is how I read the SQL standard. Are there plans to implement the
CREATE SCHEMA command that way? I think I recall someone from Toronto
mentioning something along these lines.
Obviously, this command style would be mostly equivalent to temporarily
setting the search path. We'd also need alter schema, which SQL doesn't
have.
> Given the present semantics of
> search_path, that will imply an implicit search of pg_catalog before
> foo.
Interesting ... Is that only temporary? (since you say "present"
semantics)
--
Peter Eisentraut peter_e(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2002-04-16 02:07:11 | Re: multibyte support by default |
Previous Message | Hiroshi Inoue | 2002-04-16 01:55:08 | Re: ANSI Compliant Inserts |