| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PGOPTS |
| Date: | 2006-04-19 05:29:13 |
| Message-ID: | 22288.1145424553@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Richard Broersma Jr <rabroersma(at)yahoo(dot)com> writes:
> All I could find similar to PGOPTS was PGOPTIONS. Are they equivalent? If they are, would it be
> safe to use PGOPTIONS in-place of PGOPTS in the /etc/conf.d/postgresql conf file?
There is no such animal as PGOPTS referenced anywhere in the current
Postgres source tree, so I'm not entirely sure what you think PGOPTS
does. If you are looking at the current postgresql RPM init script,
its PGOPTS is nothing more than a local shell variable in that script,
and it does nothing except what you see the script do with it (ie,
pass some command-line switches to the postmaster).
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thusitha Kodikara | 2006-04-19 06:58:27 | Different results when specifying DEFAULT values through ALTER TABLE |
| Previous Message | Richard Broersma Jr | 2006-04-19 04:49:05 | Re: PGOPTS |