| 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-04 23:27:15 |
| Message-ID: | 1207351635.81391.13.camel@localhost |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Version is 8.2.5 running on FreeBSD 6.2. I can try upgrading
to 8.2.7, if you think that would help.
I don't think I can make a test case. Database had been
up for a year now, with about 2 thousand inherited tables
(partitioning) and about 2B rows in all tables...
On Fri, 2008-04-04 at 18:58 -0400, Tom Lane wrote:
> Alex Vinogradovs <AVinogradovs(at)Clearpathnet(dot)com> writes:
> > I've got a pretty large database, and since certain time
> > it started giving me "too many LWLocks taken" when running
> > some batch inserts... Any parameter can be ajusted ?
>
> Oh really? That's a bug, not something you need to adjust a parameter
> for. Can you put together a self-contained test case? What PG
> version is this?
>
> regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2008-04-05 00:15:40 | Re: too many LWLocks taken |
| Previous Message | Markus Wollny | 2008-04-04 23:11:50 | Re: Duplicate Key violation on dump&reload using pg_restore |