| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Dronamraju Rajesh <drajesh80(at)yahoo(dot)com> |
| 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:08:14 |
| Message-ID: | 15442.976601294@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vijayendra mohan agrawal | 2000-12-12 06:09:09 | JDBC Driver |
| Previous Message | Dronamraju Rajesh | 2000-12-12 05:55:52 | LockReplace: xid table corrupted |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dronamraju Rajesh | 2000-12-12 06:28:38 | Re: [BUGS] LockReplace: xid table corrupted |
| Previous Message | Dronamraju Rajesh | 2000-12-12 05:55:52 | LockReplace: xid table corrupted |