Craig Ringer <[EMAIL PROTECTED]> writes:
> I've just hit a reproducible error with a query that uses pg_trgm:
> ERROR: too many LWLocks taken
This is absolutely a bug. Please send a complete test case to
pgsql-bugs.
regards, tom lane
--
Sent via pgsql-general mailing l
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 <[E
Alex Vinogradovs <[EMAIL PROTECTED]> 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 oth
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 -04
Alex Vinogradovs <[EMAIL PROTECTED]> 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. C
