On Monday 01 March 2010 @ 17:58, Tom Lane wrote:
> "Ed L." <pgsql(at)bluepolka(dot)net> writes:
> > Killed the stuck postmaster with sigkill, edited the file,
> > restarted postmaster, and it re-wrote the file with the
> > bogus entry.  I don't have any superuser sessions open.  Is
> > there another route?
> 
> What you're going to need to do is stop the postmaster, start
> a standalone backend (see the "postgres" man page entry if you
> never did that before) and issue the ALTER USER in the
>  standalone backend.  Then you can restart normal operations.

That did the trick.  Thank you very much, Sensei.

Ed

In response to

• Re: Hung postmaster (8.3.9) at 2010-03-02 00:58:49 from Tom Lane

Responses

• Re: [SOLVED] Re: Hung postmaster (8.3.9) at 2010-03-02 01:29:56 from Tom Lane

pgsql-hackers by date

Next:	From: Tom Lane	Date: 2010-03-02 01:29:56
	Subject: Re: [SOLVED] Re: Hung postmaster (8.3.9)
Previous:	From: Tom Lane	Date: 2010-03-02 01:04:11
	Subject: Re: Re: Hot Standby query cancellation and Streaming Replication integration

pgsql-general by date

Next:	From: Tom Lane	Date: 2010-03-02 01:29:56
	Subject: Re: [SOLVED] Re: Hung postmaster (8.3.9)
Previous:	From: Tom Lane	Date: 2010-03-02 00:58:49
	Subject: Re: Hung postmaster (8.3.9)