| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-patches <pgsql-patches(at)postgresql(dot)org> |
| Subject: | Re: [BUGS] 8.0: Absolute path required for INITDB? |
| Date: | 2004-08-16 16:23:47 |
| Message-ID: | 200408161623.i7GGNlv23530@candle.pha.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
Andrew Dunstan wrote:
>
>
> Bruce Momjian wrote:
>
> >Patch to throw an error if -L is not an abolute path attached and
> >applied.
> >
> >
>
>
> Why are we placing this restriction? What Josh tried to do seems
> perfectly reasonable to me. Rather I would ask why we changed the
> description-loading routine in version 1.7 of initdb.c to use a copy
> from file instead of what happens everywhere else where initdb loads the
> file and feeds it to the postgres stdin? And if we want to keep doing
> that rather than being consistent with the rest of initdb, can't we just
> make sure we make the path absolute?
I am fine with that if someone wants to code it. I just did the minimal
to prevent strange failures.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-08-16 16:34:34 | Re: [BUGS] 8.0: Absolute path required for INITDB? |
| Previous Message | Tom Lane | 2004-08-16 16:21:32 | Re: [BUGS] 8.0: Absolute path required for INITDB? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2004-08-16 16:34:34 | Re: [BUGS] 8.0: Absolute path required for INITDB? |
| Previous Message | Tom Lane | 2004-08-16 16:21:32 | Re: [BUGS] 8.0: Absolute path required for INITDB? |