| From: | Alex Vinogradovs <AVinogradovs(at)Clearpathnet(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: too many LWLocks taken |
| Date: | 2008-04-07 16:19:09 |
| Message-ID: | 1207585149.81391.26.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
It appears the errors were caused by table corruption. I've
truncated and reloaded some large table (300m entries),
and the problem disappeared. Table corruption was probably
caused by hardware failure, not by PostgreSQL :)
On Fri, 2008-04-04 at 20:15 -0400, Tom Lane wrote:
> Alex Vinogradovs <AVinogradovs(at)Clearpathnet(dot)com> writes:
> > Version is 8.2.5 running on FreeBSD 6.2. I can try upgrading
> > to 8.2.7, if you think that would help.
>
> Well, an upgrade would be a good idea on general principles, but
> I doubt it will fix a previously unknown bug.
>
> Does the postmaster log show any other odd behavior around these
> errors? Which process is throwing the error anyway? If it's
> a regular backend, what query is it executing?
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua D. Drake | 2008-04-07 16:28:53 | Re: edb-debugger, debugging pl/pgsql |
| Previous Message | Tony Caduto | 2008-04-07 15:31:18 | Re: edb-debugger, debugging pl/pgsql |