| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Ed L(dot)" <pgsql(at)bluepolka(dot)net> |
| Cc: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Hung postmaster (8.3.9) |
| Date: | 2010-03-02 00:58:49 |
| Message-ID: | 28647.1267491529@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
"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.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed L. | 2010-03-02 01:26:20 | [SOLVED] Re: Hung postmaster (8.3.9) |
| Previous Message | Tom Lane | 2010-03-02 00:57:09 | Re: Hung postmaster (8.3.9) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2010-03-02 01:04:11 | Re: Re: Hot Standby query cancellation and Streaming Replication integration |
| Previous Message | Tom Lane | 2010-03-02 00:57:09 | Re: Hung postmaster (8.3.9) |