Will this make it into 8.1?
>-Original Message-
>From: Tom Lane [mailto:[EMAIL PROTECTED]
>Sent: Thursday, January 27, 2005 7:38 PM
>To: Kenneth Lareau
>Cc: David Parker; pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Strange issue with initdb on 8.0 and
&
Yes, thanks very much!
- DAP
>-Original Message-
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED] On Behalf Of Kenneth Lareau
>Sent: Thursday, January 27, 2005 8:10 PM
>To: Tom Lane
>Cc: Kenneth Lareau; pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Stra
In message <[EMAIL PROTECTED]>, Tom Lane writes:
>Kenneth Lareau <[EMAIL PROTECTED]> writes:
>> In message <[EMAIL PROTECTED]>, Tom Lane writes:
>>> Could you truss that and see what it does?
>
>> Here's the relevant truss output from 'mkdir /software/postgresql-8.0.0'
>> on my Solaris 9 system:
>
Kenneth Lareau <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Tom Lane writes:
>> Could you truss that and see what it does?
> Here's the relevant truss output from 'mkdir /software/postgresql-8.0.0'
> on my Solaris 9 system:
> 10832: mkdir("/software/postgresql-8.0.0", 0777)
Andrew Dunstan <[EMAIL PROTECTED]> writes:
> There's also a tiny race condition, which I guess isn't worth worrying
> about.
Considering that we're not checking ownership or permissions of the
parent directories, I'd say not.
regards, tom lane
---
Tom Lane wrote:
I don't know why the command 'mkdir' doesn't exhibit the
same problem as the function 'mkdir', but running:
mkdir /software/postgresql-8.0.0
produces the correct error "File exists" on my system.
Could you truss that and see what it does? It would be a simpl
In message <[EMAIL PROTECTED]>, Tom Lane writes:
>Kenneth Lareau <[EMAIL PROTECTED]> writes:
>> In message <[EMAIL PROTECTED]>, Tom Lane writes:
>>> I suppose that manually creating the data directory before running
>>> initdb would also avoid this issue, since the mkdir(2) loop is only
>>> entered
Kenneth Lareau <[EMAIL PROTECTED]> writes:
> In message <[EMAIL PROTECTED]>, Tom Lane writes:
>> I suppose that manually creating the data directory before running
>> initdb would also avoid this issue, since the mkdir(2) loop is only
>> entered if we don't find the directory in existence.
> Actua
In message <[EMAIL PROTECTED]>, Tom Lane writes:
>"David Parker" <[EMAIL PROTECTED]> writes:
>> Did initdb previously just assume the -D path existed, and now it is
>> trying to create the whole path, if necessary?
>
>Pre-8.0 it was using mkdir(1), which might possibly contain some weird
>workaroun
m: Tom Lane [mailto:[EMAIL PROTECTED]
>Sent: Thursday, January 27, 2005 6:22 PM
>To: David Parker
>Cc: Kenneth Lareau; pgsql-hackers@postgresql.org
>Subject: Re: [HACKERS] Strange issue with initdb on 8.0 and
>Solaris automounts
>
>"David Parker" <[EMAIL PROTECTED]
"David Parker" <[EMAIL PROTECTED]> writes:
> Did initdb previously just assume the -D path existed, and now it is
> trying to create the whole path, if necessary?
Pre-8.0 it was using mkdir(1), which might possibly contain some weird
workaround for this case on Solaris.
I suppose that manually cr
ehalf Of Kenneth Lareau
>Sent: Thursday, January 27, 2005 5:23 PM
>To: pgsql-hackers@postgresql.org
>Subject: [HACKERS] Strange issue with initdb on 8.0 and
>Solaris automounts
>
>Folks,
>
>I ran into an interesting issue when installing PostgreSQL 8.0
>that I'm not
Folks,
I ran into an interesting issue when installing PostgreSQL 8.0 that I'm
not sure how to resolve correctly. My system is a Sun machine (Blade
1000) running Solaris 9, with relatively recent patches. After install-
ing 8.0, I went to run the 'initdb' command and was greeted with the
followin
13 matches
Mail list logo
