It usually refers to some cached plan referring to a table or object that does not exist anymore. Do you have stored procedures that refer to tables that are deleted? This includes temporary tables.
So maybe it's only happening when a certain stored procedure is executed twice in the same session? Hope this helps, On Mon, Aug 18, 2003 at 01:01:53PM +0000, Jeff Boes wrote: > What might be the source of this error? > > Cache lookup failed for relation 188485009 > > We've been getting these at odd intervals, and they are not reproducible. > > Our setup: > > PostgreSQL 7.3.3 > Red Hat 7.3 > > kernel.shmall = 1352914698 > kernel.shmmax = 1352914698 > > shared_buffers = 131072 > max_fsm_pages = 350000 > max_fsm_relations = 200 > wal_buffers = 32 > sort_mem = 65536 > vacuum_mem = 65536 > effective_cache_size = 196608 > > -- > Jeff Boes vox 269.226.9550 ext 24 > Database Engineer fax 269.349.9076 > Nexcerpt, Inc. http://www.nexcerpt.com > ...Nexcerpt... Extend your Expertise > > > ---------------------------(end of broadcast)--------------------------- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org -- Martijn van Oosterhout <[EMAIL PROTECTED]> http://svana.org/kleptog/ > "All that is needed for the forces of evil to triumph is for enough good > men to do nothing." - Edmond Burke > "The penalty good people pay for not being interested in politics is to be > governed by people worse than themselves." - Plato
pgp00000.pgp
Description: PGP signature
