| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | rakeshkumar464 <rakeshkumar464(at)outlook(dot)com> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: starting PG command line options vs postgresql.con |
| Date: | 2017-10-30 13:59:27 |
| Message-ID: | 16295.1509371967@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
rakeshkumar464 <rakeshkumar464(at)outlook(dot)com> writes:
> I am new to Docker env and I see that PG, as a container is started with
> [ lots of command-line parameters ]
> I would prefer using postgresql.conf. what is the consensus in this forum
> regarding command line vs postgresql.conf. Also if conflicting, which one
> takes priority.
The command line takes priority, IIRC, which means that nothing set on
the command line can be overridden without a restart.
I like to specify -p on the command line so that it's easy to tell which
postmaster is which in "ps" listings (of course, this only matters if
you're running multiple postmasters). Otherwise it's better to leave
as much as you can to postgresql.conf.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2017-10-30 14:08:07 | Re: starting PG command line options vs postgresql.con |
| Previous Message | rakeshkumar464 | 2017-10-30 13:48:45 | starting PG command line options vs postgresql.con |