Received: from cygnus.com (runyon.sfbay.redhat.com [205.180.230.5] (may be forged)) by postgresql.org (8.11.3/8.11.4) with SMTP id g0ML2fl90295 for ; Tue, 22 Jan 2002 16:02:41 -0500 (EST) (envelope-from fnasser@redhat.com) Received: from redhat.com (rtl.sfbay.redhat.com [205.180.230.21]) by runyon.cygnus.com (8.8.7-cygnus/8.8.7) with ESMTP id NAA12269; Tue, 22 Jan 2002 13:02:34 -0800 (PST) Message-ID: <3C4DD34F.CC4D8B6@redhat.com> Date: Tue, 22 Jan 2002 16:02:07 -0500 From: Fernando Nasser Organization: Red Hat Canada X-Mailer: Mozilla 4.78 [en] (X11; U; Linux 2.4.9-13 i686) X-Accept-Language: en MIME-Version: 1.0 To: Tom Lane CC: Peter Eisentraut , pgsql-hackers@postgresql.org Subject: Re: RFD: schemas and different kinds of Postgres objects References: <12239.1011661590@sss.pgh.pa.us> <3C4D8A39.FF79CDC4@redhat.com> <15339.1011716171@sss.pgh.pa.us> <3C4D96C5.80BBF764@redhat.com> <15638.1011718290@sss.pgh.pa.us> <3C4DCBDB.689D7201@redhat.com> <28199.1011732109@sss.pgh.pa.us> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200201/993 X-Sequence-Number: 17985 Tom Lane wrote: > > Huh? You seem to be assuming that we need to support both the > historical Postgres behavior and the SQL-standard behavior with exactly > the same configuration switches. That's not how I'm seeing it at all. > The way I'm envisioning it, you could get either the historical > behavior, or the standard's behavior, depending on how you set up the > configuration variables. Then we can live just with the schema being the ownership. Switches set to standard: schema search path = ("user's own schema", postgres) [ default creation schema = user's own schema ] same as below, we don't need this switch Switches set to historical: schema search path = (user's own schema, "any" schema, postgres) [ default creation schema = user's own schema ] The searching in "any" schema (i.e., any owner) will let will find things that where defined the way they are today, i.e., possibly by several different users. P.S.: You can even add the "default" schema in the standard case and I believe you are still compliant and can handle things easier: schema search path = ("user's own schema", postgres) Maybe you could give an example of a case where the schema meaning ownership breaks things. Or what kind of additional things you have in mind that would require orthogonal schema and ownership spaces. Regards, Fernando -- Fernando Nasser Red Hat Canada Ltd. E-Mail: fnasser@redhat.com 2323 Yonge Street, Suite #300 Toronto, Ontario M4P 2C9