Skip site navigation (1) Skip section navigation (2)

BUG #2876: problems witih pg_ctl -w

From: "Marvin Solomon" <solomon(at)conceptshopping(dot)com>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #2876: problems witih pg_ctl -w
Date: 2007-01-10 12:39:10
Message-ID: 200701101239.l0ACdAZT000519@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      2876
Logged by:          Marvin Solomon
Email address:      solomon(at)conceptshopping(dot)com
PostgreSQL version: 8.2.1
Operating system:   Windows XP
Description:        problems witih pg_ctl -w
Details: 

The "-w" option to pg_ctl on Windows systems has a 
couple of problems.

The main problem is that it attempts to detect 
whether the server is running by establishing a
session, but provides no way to supply a user name
for that attempt.  The default is to use your
login name, but that may not correspond to any
user name in the database.  Here's an example:

    % pg_ctl start -w -l log
    waiting for server to start...........^C
    % cat foo
    LOG:  database system was shut down at 2007-01-10 05:56:57 CST
    LOG:  checkpoint record is at 0/34ACBE0
    LOG:  redo record is at 0/34ACBE0; undo record is at 0/0; shutdown TRUE
    LOG:  next transaction ID: 0/686; next OID: 16572
    LOG:  next MultiXactId: 1; next MultiXactOffset: 0
    LOG:  database system is ready
    FATAL:  role "solomon" does not exist
    FATAL:  role "solomon" does not exist
    FATAL:  role "solomon" does not exist 
    FATAL:  role "solomon" does not exist 
    LOG:  received fast shutdown request
    LOG:  shutting down
    LOG:  database system is shut down
    
I note that the code explicity checks for the
error "no password supplied", but not for "role
does not exist".

Another problem is that the max time to wait is 
wired in at 60 seconds.  It would be nice if there
were some way to supply a different value.

pgsql-bugs by date

Next:From: Ravalison FrederykDate: 2007-01-10 13:00:50
Subject: BUG #2877: Caused by: org.postgresql.util.PSQLException: Unknown Response Type
Previous:From: Marco BehnkeDate: 2007-01-10 11:26:13
Subject: Bugreport

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group