Re: BUG #13583: Documentation "5.8.2. The Public Schema" misleading

On Thu, Aug 20, 2015 at 2:14 PM, John McKown <john(dot)archie(dot)mckown(at)gmail(dot)com>
wrote:

> 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.​
>

So basically the key phrase in that paragraph is "by default". The reader
is intended to take that to mean "with only the schemas created by initdb".

Now, maybe this should be explained before teaching the user to create
schemas...

​The assumption of there not being a username schema is implicit here and
everything works if that is true. But the most of this could be better
written to either directly account for the username schema or separately
explain the interaction when one is present.

​Room for improvement but not exactly critical.

David J.