From: | John McKown <john(dot)archie(dot)mckown(at)gmail(dot)com> |
---|---|
To: | mina(at)naguib(dot)ca |
Cc: | pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #13583: Documentation "5.8.2. The Public Schema" misleading |
Date: | 2015-08-20 18:14:49 |
Message-ID: | CAAJSdjiGGG_mrRiKGSWuhSAZ7eiFxbTWWo2ZykCriiingq3v5A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Thu, Aug 20, 2015 at 12:51 PM, <mina(at)naguib(dot)ca> wrote:
> The following bug has been logged on the website:
>
> Bug reference: 13583
> Logged by: Mina Naguib
> Email address: mina(at)naguib(dot)ca
> PostgreSQL version: 9.5alpha2
> Operating system: N/A
> Description:
>
> This section of the documentation states:
>
> "... we created tables without specifying any schema ... are automatically
> put into a schema named "public" ..."
>
> This is not true. At least from my tests, the search_path is taken into
> account.
>
> My search_path is set to "$user",public, and therefore a barebones "create
> table foo();" creates the table foo in the "mina" schema, not the "public"
> schema.
>
>
>
I think this depends on you, the user, creating the proper schema. I don't
think that an "initdb" creates any schemas other than "public". At least,
that has been my experience so far.
--
Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.
Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
He's about as useful as a wax frying pan.
10 to the 12th power microphones = 1 Megaphone
Maranatha! <><
John McKown
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2015-08-20 19:03:07 | Re: BUG #13583: Documentation "5.8.2. The Public Schema" misleading |
Previous Message | Jeff Janes | 2015-08-20 18:11:00 | Re: BUG #13583: Documentation "5.8.2. The Public Schema" misleading |