By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
425,979 Members | 943 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 425,979 IT Pros & Developers. It's quick & easy.

ERRORs after upgrade from 7.2.1 to 7.4 about nonexisting large objects

P: n/a
Hi,

sorry for reposting, but it seems my message just hit nothing
but air. If I posted to the wrong list or did something else
wrong with the message, please let me know.

I really want to know what's going on but still found nothing.
I do not know when and where the statements are produced that
lead to the error messages. It seems they were generated by
postgres internally but I cannot see when and why. How can
I find out? I want to stop those errors.

-dirk

-------------8<-------------8<------------8<------------

Hi all,

a few days ago, I upgraded from PostgreSQL 7.2.1 to 7.4, following
the instructions in the INSTALL file, including dump and restore.
All this worked fine without any error (message).

Since then, I found lots of the following in the postmaster output:

2003-11-29 15:19:54 [1359] ERROR: large object 4838779 does not exist
2003-11-29 15:20:11 [1649] ERROR: large object 4838779 does not exist
2003-11-29 15:20:11 [1657] ERROR: large object 4838779 does not exist
2003-11-29 15:20:27 [1732] ERROR: large object 4838779 does not exist
2003-11-29 15:20:49 [1956] ERROR: large object 10204242 does not exist
2003-11-29 15:20:49 [1975] ERROR: large object 4838779 does not exist
2003-11-29 15:21:49 [2784] ERROR: large object 10204242 does not exist
2003-11-29 15:21:56 [3150] ERROR: large object 10204242 does not exist
2003-11-29 15:22:49 [4053] ERROR: large object 10204242 does not exist
2003-11-29 15:23:06 [4132] ERROR: large object 4838779 does not exist
2003-11-29 15:24:47 [5114] ERROR: large object 4838779 does not exist
2003-11-29 15:26:09 [6259] ERROR: large object 4838779 does not exist
2003-11-29 15:26:27 [6515] ERROR: large object 10204242 does not exist

I cannot find the source of those errors. It seems that everything is
basically working, but there are always those errors about the two
large objects.
I'd like to find out what went wrong and how I can repair it. I couldn't
find anything in the docs and the mailing lists.

To give more information about the messages, here are two more detailed
outputs, one per id:

003-11-29 21:42:43 [2533] LOG: 00000: statement: BEGIN
LOCATION: pg_parse_query, postgres.c:464
2003-11-29 21:42:43 [2533] LOG: 00000: statement: select proname, oid from
pg_proc where proname = 'lo_open'

or proname = 'lo_close' or proname = 'lo_creat'
or proname = 'lo_unlink' or proname =
'lo_lseek'
or proname = 'lo_tell' or
proname = 'loread' or proname = 'lowrite'
LOCATION: pg_parse_query, postgres.c:464
2003-11-29 21:42:43 [2533] ERROR: 42704: large object 10204242 does not exist
LOCATION: inv_open, inv_api.c:128
2003-11-29 21:42:43 [2533] LOG: 00000: statement: ROLLBACK

----------8<---------8<--------------

2003-11-29 21:43:48 [3047] LOG: 00000: statement: BEGIN
LOCATION: pg_parse_query, postgres.c:464
2003-11-29 21:43:48 [3047] LOG: 00000: statement: select proname, oid from
pg_proc where proname = 'lo_open'

or proname = 'lo_close' or proname = 'lo_creat'
or proname = 'lo_unlink' or proname =
'lo_lseek'
or proname = 'lo_tell' or
proname = 'loread' or proname = 'lowrite'
LOCATION: pg_parse_query, postgres.c:464
2003-11-29 21:43:48 [3057] LOG: 00000: statement: set datestyle to 'ISO';
select version(), case when pg_encoding_to_char(1) = 'SQL_ASCII' then
'UNKNOWN' else get
databaseencoding() end;
LOCATION: pg_parse_query, postgres.c:464
2003-11-29 21:43:48 [3047] ERROR: 42704: large object 4838779 does not exist
LOCATION: inv_open, inv_api.c:128
2003-11-29 21:43:48 [3047] LOG: 00000: statement: ROLLBACK

The logged statements seems to suggest that there went something wrong with
the template database creation or maybe the dump/restore. But as I wrote
earlier: There was no visible error.

-dirk

--
D i r k F "o r s t e r l i n g
r@zorbla.de http://r@zorbla.de/
-------------
A child of five could understand this. Fetch me a child of five!

---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster

Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a

Well, maybe I forgot to mention that I'm not aware of any large objects
that had to be migrated. All data I put into the db was just VARCHARs,
INTEGERs and some SERIALs.

How can I find out more about the "missing" objects and where they are
queried?

Dirk Försterling wrote:
2003-11-29 15:19:54 [1359] ERROR: large object 4838779 does not exist


-dirk

--
D i r k F "o r s t e r l i n g
r@zorbla.de http://r@zorbla.de/
-------------
"Das ist aber gerade e hoch 3 z. Das sieht doch jeder!" - R.K.
---------------------------(end of broadcast)---------------------------
TIP 8: explain analyze is your friend

Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.