Skip site navigation (1) Skip section navigation (2)

Re: [BUGS] LockReplace: xid table corrupted

From: Dronamraju Rajesh <drajesh80(at)yahoo(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-admin(at)postgresql(dot)org, pgsql-bugs(at)postgresql(dot)org
Subject: Re: [BUGS] LockReplace: xid table corrupted
Date: 2000-12-12 06:28:38
Message-ID: 20001212062838.40148.qmail@web9603.mail.yahoo.com (view raw or flat)
Thread:
Lists: pgsql-adminpgsql-bugs
thanks tom....But strange thing is that my database
has only 15 tables totally...which are very small
too...

so how would be the way of me reaching to 1000
tables???

and why do i get an error message "sorry too many
clients" ??? 

Regards
Rajesh
--- Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dronamraju Rajesh <drajesh80(at)yahoo(dot)com> writes:
> > database:- Postgres 6.5.2 ( pl dont suggest to
> upgrade
> > to 7.0.2. once this problem is solved. then i can
> do
> > testing of my app with postgres 7.0.2)
> 
> If you update to 7.0.3, you'll probably find this
> problem
> goes away.  It sounds to me like you are running
> into a bogus
> debug check in the older code that assumed
> LockRelease should
> never need to release more than a thousand locks.
> 
> If you don't want to update, try not touching 1000
> tables in
> the same transaction.  I'm guessing you do a lot of
> large-object
> slinging ... otherwise it's not that easy to get to
> 1000 ...
> 
> 			regards, tom lane


__________________________________________________
Do You Yahoo!?
Yahoo! Shopping - Thousands of Stores. Millions of Products.
http://shopping.yahoo.com/

Responses

pgsql-admin by date

Next:From: Rainer MagerDate: 2000-12-12 09:50:50
Subject: RE: LockReplace: xid table corrupted
Previous:From: vijayendra mohan agrawalDate: 2000-12-12 06:09:09
Subject: JDBC Driver

pgsql-bugs by date

Next:From: Rainer MagerDate: 2000-12-12 09:50:50
Subject: RE: LockReplace: xid table corrupted
Previous:From: Tom LaneDate: 2000-12-12 06:08:14
Subject: Re: [BUGS] LockReplace: xid table corrupted

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group