| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> |
| Cc: | Andrew Sullivan <andrew(at)libertyrms(dot)info>, HACKERS <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: (A) native Windows port |
| Date: | 2002-07-07 03:56:42 |
| Message-ID: | 6254.1026014202@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Lamar Owen <lamar(dot)owen(at)wgcr(dot)org> writes:
>> What it *does* do is effectively mask a DBA error.
> This is a satisfactory answer. In the context of the RPM distribution, if the
> initscript is used the DBA error probability is greatly reduced, thus the
> initscript can safely initdb.
Fair enough --- if the upper-layer script thinks it has enough safeties
in place, let it auto-initdb. I just don't think the postmaster should
do that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-07-07 04:12:47 | Re: Odd new symptom - database locking up on a query |
| Previous Message | Doug Fields | 2002-07-07 03:40:08 | Re2: Odd new symptom - database locking up on a query |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Eisentraut | 2002-07-07 10:58:07 | Re: Proposal: CREATE CONVERSION |
| Previous Message | Patrick Macdonald | 2002-07-07 03:44:58 | Re: Issues Outstanding for Point In Time Recovery (PITR) |