Thread: RelationClearRelation: relation X deleted while still in use???
I seem to be getting some bogus "RelationClearRelation: relation
2678605 deleted while still in use" errors. Has anyone seen this
before? This is with only one process running and after a fresh
vacuum. I can fix it by re-running the vacuum and then rerunning
the query. It seems to be random as sometimes but not always I
can simply re-run the query without doing a vacuum and it works
fine the second time.
I'd be happy to hear about a workaround or maybe even a fix.
I have PostgreSQL 7.2.1 running under Solaris 8 on an Intel box.
The database is moderate size, on order 100K rows in some tables.
I can't seem to reproduce the error with anything less then my
full 10K lines of code application.
Here is an Excerpt from my program's log file. It first
prints the error returned from the back end and them prints
the SQL it sent.
ERROR SQL command failed:
ERROR: RelationClearRelation: relation 2678605 deleted while still in
use
ERROR SQL Statment that failed:
select count(location.sequence)
from location, measurement, format, vehicle
where
measurement.name = 'WWB001N' AND
vehicle.project = '401' AND
vehicle.vehicle = '001' AND
vehicle.rev = 'T' AND
format.format_type = 'VEHCENTAUR' AND
location.measurement_id = measurement.measurement_id AND
measurement.format_id = format.format_id AND
format.vehicle_id = vehicle.vehicle_id;
=====
Chris Albertson
Home: 310-376-1029 chrisalbertson90278@yahoo.com
Cell: 310-990-7550
Office: 310-336-5189 Christopher.J.Albertson@aero.org
__________________________________________________
Do You Yahoo!?
Sign up for SBC Yahoo! Dial - First Month Free
http://sbc.yahoo.com
Chris Albertson <chrisalbertson90278@yahoo.com> writes:
> I seem to be getting some bogus "RelationClearRelation: relation
> 2678605 deleted while still in use" errors. Has anyone seen this
> before?
Lots of times on old releases. Are you *sure* you are running 7.2.1?
regards, tom lane
I did check the mail list archives and on google and you are right the problem has not come up recently, until now it seems. Yes I am running 7.2.1. (see below) I'd be happy to try any tests you might want me too but as I said, I can't make it happen with a simple stripped down test case. I need the full 10K line application and a well populated set of tables. Also it is random, only happens now and then. My application (storing telemetry data formats for space lift bosters.) does on order of 100,000 queries (mostly three way joins) per run and this happens maybe once in 15 runs. I think this is a real bug. I can run the same exact SELECT query twice and it fails one and works on the second try. I do have a workaround but you may want to investigate as there is likely an underlaying problem remaining. All my software is recent. The disk drive in this Solaris PC "smoked" last month and I re-built it with a bare unformatted drive. Also you can see how I checked the version below wi792:~>which postmaster /usr/local/pgsql/bin/postmaster wi792:~>strings /usr/local/pgsql/bin/postmaster | grep "(PostgreSQL)" postmaster (PostgreSQL) 7.2.1 postgres (PostgreSQL) 7.2.1 As you can see the sign on message compiled into the executable image says "7.2.1". Is there is better way to check? --- Tom Lane <tgl@sss.pgh.pa.us> wrote: > Chris Albertson <chrisalbertson90278@yahoo.com> writes: > > I seem to be getting some bogus "RelationClearRelation: relation > > 2678605 deleted while still in use" errors. Has anyone seen this > > before? > > Lots of times on old releases. Are you *sure* you are running 7.2.1? > > regards, tom lane ===== Chris Albertson Home: 310-376-1029 chrisalbertson90278@yahoo.com Cell: 310-990-7550 Office: 310-336-5189 Christopher.J.Albertson@aero.org __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com
Chris Albertson <chrisalbertson90278@yahoo.com> writes:
> I do have a workaround but you may want to investigate as there
> is likely an underlaying problem remaining.
Perhaps, but without a reproducible test case there's dang little
I can do.
> As you can see the sign on message compiled into the executable
> image says "7.2.1". Is there is better way to check?
This proves *zero* about what you are actually talking to. What
do you get from "select version()" in psql?
regards, tom lane
--- Tom Lane <tgl@sss.pgh.pa.us> wrote: > Chris Albertson <chrisalbertson90278@yahoo.com> writes: > > I do have a workaround but you may want to investigate as there > > is likely an underlaying problem remaining. > > Perhaps, but without a reproducible test case there's dang little > I can do. It is a "C" program that triggers the error. I have logic in my code that detects this error. I can do just about anything at that point. I can work on this but would need some hints. Yes you are right, I could be running some other executable. _I_ know there is no older one laying around but can't prove it to you. I should print the results of "select version() to my log file as well as the hostname, databasename, and so on when any error is detected. > > > As you can see the sign on message compiled into the executable > > image says "7.2.1". Is there is better way to check? > > This proves *zero* about what you are actually talking to. What > do you get from "select version()" in psql? > > regards, tom lane ===== Chris Albertson Home: 310-376-1029 chrisalbertson90278@yahoo.com Cell: 310-990-7550 Office: 310-336-5189 Christopher.J.Albertson@aero.org __________________________________________________ Do You Yahoo!? Sign up for SBC Yahoo! Dial - First Month Free http://sbc.yahoo.com