Re: can't startup PG-8.0.3

From: Ruslan A Dautkhanov <rusland(at)scn(dot)ru>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: can't startup PG-8.0.3
Date: 2005-06-27 03:09:24
Message-ID: 42BF6DE4.3070008@scn.ru
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hello !

Tom Lane wrote:

>>I have a command
>> su - pgsql -c '/usr/local/pgsql/bin/postmaster -d 5 -D
>>/usr/local/pgsql/data'
>>
>>
>
>Shouldn't there be an & or something in there? Seems like that will
>leave the su command blocked waiting for the postmaster to exit,
>which of course it should not.
>
>
>
I try to use &, this did not help.

>>I even tries to use ktrace(1) :
>> ktrace su - pgsql -c '/usr/local/pgsql/bin/postmaster -d 5 -D
>>/usr/local/pgsql/data'
>>
>>
>
>That won't tell you anything --- the trace will only trace what "su" does.
>Better to su to pgsql and ktrace the postmaster directly.
>
>
Yes, you're right. The ktrace dump for postmaster process:
su - pgsql -c 'ktrace /usr/local/pgsql/bin/postmaster -i -d 5 -D
/usr/local/pgsql/data' :

...
86611 postgres RET write 44/0x2c
86611 postgres CALL gettimeofday(0xbfbfd5a8,0)
86611 postgres RET gettimeofday 0
86611 postgres CALL getpid
86611 postgres RET getpid 86611/0x15253
86611 postgres CALL sendto(0x5,0xbfbfda80,0x60,0,0,0)
86611 postgres GIO fd 5 wrote 96 bytes
"<135>Jun 27 11:02:02 postgres[86611]: [569-1] %DEBUG:
-----------------------------------------"
86611 postgres RET sendto 96/0x60
86611 postgres CALL write(0x2,0x82eb128,0x33)
86611 postgres GIO fd 2 wrote 51 bytes
"%DEBUG: -----------------------------------------
"
86611 postgres RET write 51/0x33
86611 postgres CALL fork
86611 postgres RET fork 86612/0x15254
86611 postgres CALL exit(0)

I'll keep try to startup PostgreSQL 8.0.3... Thanks

--
Ruslan A Dautkhanov

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Ruslan A Dautkhanov 2005-06-27 04:17:07 Re: can't startup PG-8.0.3
Previous Message Tom Lane 2005-06-26 19:44:09 Re: Works as SELECT but not as a VIEW