Re: 9.4 Proposal: Initdb creates a single table - Mailing list pgsql-hackers

From Albe Laurenz
Subject Re: 9.4 Proposal: Initdb creates a single table
Date
Msg-id A737B7A37273E048B164557ADEF4A58B17CF2FCB@ntex2010i.host.magwien.gv.at
Whole thread Raw
In response to Re: 9.4 Proposal: Initdb creates a single table  (Craig Ringer <craig@2ndquadrant.com>)
List pgsql-hackers
Craig Ringer wrote:
>> Good that you mention that!  I have wondered what to do with it.
>> When I first connected to PostgreSQL, I created a sample table, but the
>> senior developer from the other office told me that this is the "postgres"
>> database and that I shouldn't create any objects there.
>>
>> What is it good for?  Can I delete it?
> 
> A key difference between the "postgres" DB and a default table is that
> the "postgres" DB is very convenient with PostgreSQL's default of
> connecting to a DB of the same name as the user.

I did not seriously want to dispute the value of the "postgres" DB,
I just think that making things easier to understand for the newbie
is *not* its greatest merit.

It is mostly for the convenience of the administrator, right?

Yours,
Laurenz Albe

pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: 9.4 Proposal: Initdb creates a single table
Next
From: Andres Freund
Date:
Subject: Re: What use case is make_tuple_indirect() supposed to illustrate?