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

Re: [HACKERS] Table corrupt?

From: Brandon Ibach <bibach(at)infomansol(dot)com>
To: vadim(at)krs(dot)ru (Vadim Mikheev)
Cc: hackers(at)postgresql(dot)org (PostgreSQL Hackers)
Subject: Re: [HACKERS] Table corrupt?
Date: 1998-06-10 01:37:40
Message-ID: 199806100137.UAA23616@vweb.infomansol.com (view raw or flat)
Thread:
Lists: pgsql-hackers
Vadim Mikheev said:
> 
> Well, could you use gdb to attach to backend runnig vacuum ?
> 
> Vadim
> 
   Okay... using pg_dump to get the data out of the table is causing
much the same situation.  I did a backtrace in gdb, but unfortnately,
I'm running a copy of postgres without debugging symbols, so it may be
of limited use.  Here 'tis...

#0  0x80b7590 in WaitIO ()
#1  0x80b6e3c in BufferAlloc ()
#2  0x80b6c6d in ReadBufferWithBufferLock ()
#3  0x80b7390 in ReleaseAndReadBuffer ()
#4  0x8065b90 in heapgettup ()
#5  0x80660a5 in heap_getnext ()
#6  0x8088c61 in SeqNext ()
#7  0x8084480 in ExecScan ()
#8  0x8088ca3 in ExecSeqScan ()
#9  0x80833ce in ExecProcNode ()
#10 0x8082a61 in ExecutePlan ()
#11 0x8082644 in ExecutorRun ()
#12 0x80c1577 in ProcessQueryDesc ()
#13 0x80c15d6 in ProcessQuery ()
#14 0x80c0048 in pg_eval_dest ()
#15 0x80bff56 in pg_eval ()
#16 0x80c0ff1 in PostgresMain ()
#17 0x808f7af in main ()
#18 0x805e1ab in _start ()

   I'll see about getting a trace out of a version of postgres with
debugging symbols.

-Brandon :)

pgsql-hackers by date

Next:From: Brandon IbachDate: 1998-06-10 01:58:57
Subject: Re: [HACKERS] Table corrupt?
Previous:From: Brandon IbachDate: 1998-06-10 01:10:14
Subject: Re: [HACKERS] Table corrupt?

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