Re: initdb change

From: Andrew Dunstan <andrew(at)dunslane(dot)net>
To: Robert Treat <xzilla(at)users(dot)sourceforge(dot)net>
Cc: pgsql-hackers(at)postgresql(dot)org, Joshua Drake <jd(at)commandprompt(dot)com>, David Fetter <david(at)fetter(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: initdb change
Date: 2008-08-26 21:00:59
Message-ID: 48B46F0B.4080400@dunslane.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Treat wrote:
> I would have thought the place you need this is where you have SA's who set up
> a machine, creating a $PGDATA and $PGDATA/xlog on seperate mountpoints where
> the postgres user has full rights to use those directories, but not create
> directies in those locations. In that scenario, the DBA couldn't create the
> directories if he wanted, so allowing the behavior to use an existing
> directory would be helpful.
>
>

As I have already pointed out in this thread, the allegation that you
cannot use an existing directory is false.

See below for proof.

cheers

andrew

[andrew(at)constanza inst.8.3.5707]$ sudo mkdir /bk/xl
[andrew(at)constanza inst.8.3.5707]$ sudo chown andrew:andrew /bk/xl
[andrew(at)constanza inst.8.3.5707]$ bin/initdb -X /bk/xl blurfl
The files belonging to this database system will be owned by user "andrew".
This user must also own the server process.

The database cluster will be initialized with locale en_US.UTF-8.
The default database encoding has accordingly been set to UTF8.
The default text search configuration will be set to "english".

creating directory blurfl ... ok
fixing permissions on existing directory /bk/xl ... ok
creating subdirectories ... ok
selecting default max_connections ... 100
selecting default shared_buffers/max_fsm_pages ... 32MB/204800
creating configuration files ... ok
creating template1 database in blurfl/base/1 ... ok
initializing pg_authid ... ok
initializing dependencies ... ok
creating system views ... ok
loading system objects' descriptions ... ok
creating conversions ... ok
creating dictionaries ... ok
setting privileges on built-in objects ... ok
creating information schema ... ok
vacuuming database template1 ... ok
copying template1 to template0 ... ok
copying template1 to postgres ... ok

WARNING: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the -A option the
next time you run initdb.

Success. You can now start the database server using:

bin/postgres -D blurfl
or
bin/pg_ctl -D blurfl -l logfile start

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Jaime Casanova 2008-08-26 22:57:16 Re: September Commit Fest coming soon!
Previous Message Robert Treat 2008-08-26 20:46:33 Re: initdb change