CVS Head: Pg_ctl bug? - Mailing list pgsql-bugs

From Dave Page
Subject CVS Head: Pg_ctl bug?
Date
Msg-id E7F85A1B5FF8D44C8A1AF6885BC9A0E4AC9CF6@ratbert.vale-housing.co.uk
Whole thread Raw
Responses Re: CVS Head: Pg_ctl bug?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
I just noticed that if I don't specify a data directory either on the
command line or in $PGDATA,, pg_ctl fails silently on Windows (haven't
been able to test other platforms atm). Is this a bug or an oversight -
an error message would seem appropriate?

/D

postgres@PC30:/usr/local/pgsql$ bin/pg_ctl start
postgres@PC30:/usr/local/pgsql$ bin/pg_ctl -D data start
postmaster starting
postgres@PC30:/usr/local/pgsql$ LOG:  database system was interrupted at
2005-08-29 00:34:07 GMT Standard Time
LOG:  checkpoint record is at 0/39F218
LOG:  redo record is at 0/39F218; undo record is at 0/0; shutdown TRUE
LOG:  next transaction ID: 1478; next OID: 16392
LOG:  next MultiXactId: 1; next MultiXactOffset: 0
LOG:  database system was not properly shut down; automatic recovery in
progress
LOG:  record with zero length at 0/39F260
LOG:  redo is not required
LOG:  database system is ready
LOG:  transaction ID wrap limit is 2147484144, limited by database
"postgres"

pgsql-bugs by date:

Previous
From: Michael Fuhr
Date:
Subject: Re: BUG #1854: SQL Bug
Next
From: "Vladimir Kanazir"
Date:
Subject: BUG #1855: usage of indexes