| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Brendon Matthews" <brendonm(at)bbtechltd(dot)com> |
| Cc: | "PostgreSQL Bugs" <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: HELP |
| Date: | 2002-09-12 13:13:24 |
| Message-ID: | 5164.1031836404@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
"Brendon Matthews" <brendonm(at)bbtechltd(dot)com> writes:
> I have been using PostgreSQL 7.2.2 for a while now on one of our live
> machines, however all of a sudden with no warning, we are no longer able to
> run any UPDATE statements on one of our databases. SELECT and INSERT
> statements have no issues.
> The error we are getting is:
> "The backend has broken the connection. Possibly the action you have
> attempted has caused it to close."
> Immediately after this call the database system restarts itself.
Sounds like a backend crash. What do you get in the postmaster log when
this happens? If there's a core file, can you provide a gdb stack
trace? (If there's not a core file, restarting the postmaster under
"ulimit -c unlimited" should allow one to be produced.)
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2002-09-12 13:32:55 | Re: _bt_check_unique checks every row in table when doing update?? |
| Previous Message | Rod Taylor | 2002-09-12 12:19:36 | Re: HELP |