| From: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
|---|---|
| To: | Bhushan Verma <verma(dot)bhushan(at)gmail(dot)com> |
| Cc: | PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: psql: FATAL: the database system is in recovery mode |
| Date: | 2009-06-24 12:25:15 |
| Message-ID: | 4A421B2B.2050606@enterprisedb.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-novice |
Bhushan Verma wrote:
>>> postmaster -D /var/lib/pgsql/data
> I am using the same command as you said.
I'm afraid I'm out of ideas on how to get the core dump then.
You could also try attaching gdb to the backend process before it
crashes, and get the backtrace from there. Something along the lines of:
postmaster -D /var/lib/pgsql/data
psql postgres ...
ps ax | grep postgres # check the PID of the backend process psql is
connected to.
gdb
gdb> attach <pid of backend>
gdb> cont
<run the query in psql that crashes>
gdb> bt
You still haven't posted the offending query, BTW. Is it a particular
one, or does it crash at random?
--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2009-06-24 12:45:54 | Re: GetTokenInformation() and FreeSid() at port/exec.c |
| Previous Message | Magnus Hagander | 2009-06-24 11:45:04 | Re: BUG #4877: LDAP auth allows empty password string |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bhushan Verma | 2009-06-24 13:22:11 | Re: psql: FATAL: the database system is in recovery mode |
| Previous Message | Heikki Linnakangas | 2009-06-24 10:38:24 | Re: psql: FATAL: the database system is in recovery mode |