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

Re: possible database corruption

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Chris Anderson <chris(at)journyx(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org, John Maddalozzo <john(at)journyx(dot)com>
Subject: Re: possible database corruption
Date: 2001-01-13 02:28:25
Message-ID: 418.979352905@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
Chris Anderson <chris(at)journyx(dot)com> writes:
> [ occasional crash in GetRawDatabaseInfo() ]

Try applying the following patch, which corresponds to a bug that I
noticed in GetRawDatabaseInfo a couple months ago: it looks at one
tuple-pointer slot too many in each page of pg_database.  Normally the
bogus slot will be ignored because it doesn't have the LP_USED bit set,
but if you create and drop databases a lot, it's possible there would
be garbage there.

If this doesn't help, please recompile the backend with -g, so that we
can see a more detailed stack backtrace.

			regards, tom lane

*** src/backend/utils/misc/database.c~	Wed Apr 12 13:16:07 2000
--- src/backend/utils/misc/database.c	Fri Jan 12 21:25:24 2001
***************
*** 180,186 ****
  		max = PageGetMaxOffsetNumber(pg);
  
  		/* look at each tuple on the page */
! 		for (i = 0; i <= max; i++)
  		{
  			int			offset;
  
--- 180,186 ----
  		max = PageGetMaxOffsetNumber(pg);
  
  		/* look at each tuple on the page */
! 		for (i = 0; i < max; i++)
  		{
  			int			offset;
  

In response to

pgsql-bugs by date

Next:From: Peter EisentrautDate: 2001-01-13 03:02:50
Subject: Re: Query Problem!!
Previous:From: Tom LaneDate: 2001-01-12 15:12:01
Subject: Re: Backend crash on query with UNION subselect

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