From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Joe Conway <mail(at)joeconway(dot)com> |
Cc: | "Hackers (PostgreSQL)" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: heads up -- subtle change of behavior of new initdb |
Date: | 2003-11-14 06:02:18 |
Message-ID: | 17410.1068789738@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
Joe Conway <mail(at)joeconway(dot)com> writes:
> I just noticed tonight that the new initdb introduced a subtle change of
> behavior. I use a shell script to automate the process of
> - rm old data directory
> - mkdir new data directory
> - initdb
> - load from pgdumpall
> Now, that second step is not needed, but as of today it produces an
> installation that won't start due to improper permissions on data
That's a bug --- evidently the "fix permissions" path of control is
wrong; can you take a look?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Shridhar Daithankar | 2003-11-14 06:36:05 | Re: Background writer process |
Previous Message | Joe Conway | 2003-11-14 05:49:58 | heads up -- subtle change of behavior of new initdb |
From | Date | Subject | |
---|---|---|---|
Next Message | Joe Conway | 2003-11-14 06:44:58 | Re: heads up -- subtle change of behavior of new initdb |
Previous Message | Joe Conway | 2003-11-14 05:49:58 | heads up -- subtle change of behavior of new initdb |