From: | Azimuddin Mohammed <azimeiu(at)gmail(dot)com> |
---|---|
To: | Francisco Olarte <folarte(at)peoplecall(dot)com> |
Cc: | pgsql-admin(at)postgresql(dot)org, pgsql-admin(at)lists(dot)postgresql(dot)org, Postgres General <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: initdb execution |
Date: | 2018-02-09 18:06:05 |
Message-ID: | CAKUuFd7duWMWAD97QjCf4c0=sfjK8RqSLRsJZqVMubw2Xc2eQA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-general |
Thanks for the reply..
Let me execute in the newly built setup.
On Fri, Feb 9, 2018 at 11:50 AM, Francisco Olarte <folarte(at)peoplecall(dot)com>
wrote:
> Azim
>
> On Fri, Feb 9, 2018 at 6:36 PM, Azimuddin Mohammed <azimeiu(at)gmail(dot)com>
> wrote:
> > Hello I have a question regrading initdb,
> > My understanding of initdb is when we execute it it will create the
> > directory structure in /data.
> > My question is when we run initdb when we already have a database running
> > and for some reason I run this command what happens to my existing actual
> > data does it get flushed out ? In that case what is the best practice
> here?
>
> I think initdb refuses to run when given an existent non empty
> directory, but cannot find anything in its doc page...
>
> Ok, after a little googling I've found "initdb will refuse to run if
> the data directory exists and already contains files; this is to
> prevent accidentally overwriting an existing installation." in the
> server setup / creating cluster docs (
> https://www.postgresql.org/docs/10/static/creating-cluster.html ).
>
> Francisco Olarte.
>
--
Regards,
Azim
From | Date | Subject | |
---|---|---|---|
Next Message | Chander Jamwal | 2018-02-11 23:56:00 | Recovery Standby Node |
Previous Message | Francisco Olarte | 2018-02-09 17:50:46 | Re: initdb execution |
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2018-02-09 18:17:15 | Re: Odd behavior with 'currval' |
Previous Message | Francisco Olarte | 2018-02-09 17:50:46 | Re: initdb execution |