| From: | "Chris White (cjwhite)" <cjwhite(at)cisco(dot)com> |
|---|---|
| To: | "'Tom Lane'" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Error seen when vacuuming pg_largeobject table |
| Date: | 2004-01-28 21:48:20 |
| Message-ID: | 001501c3e5e8$73c835a0$57976b80@amer.cisco.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Sorry no core files. The system is running with cores turned off. Next
time I will turn on cores prior to trying to debug this.
Chris
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
Sent: Wednesday, January 28, 2004 11:52 AM
To: cjwhite(at)cisco(dot)com
Cc: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Error seen when vacuuming pg_largeobject table
> Got it to happen again after a power fail. Here is the logs this time
> with verbose.
Hm, those backend crashes should have left core dumps; can you get a
stack trace from the core?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gaetano Mendola | 2004-01-28 22:15:10 | Re: Error seen when vacuuming pg_largeobject table |
| Previous Message | Frank Way | 2004-01-28 21:37:22 | How to determine which file contains which block |