Re: [HACKERS] self-deadlock at FATAL exit of boostrap process on read error

2006-06-08 Thread Tom Lane
"Qingqing Zhou" <[EMAIL PROTECTED]> writes: > "Tom Lane" <[EMAIL PROTECTED]> wrote >> Do you have a test case to reproduce this problem? > According to the error message, the problem happens during reading > pg_database. I just tried to plug in this line in mdread(): OK, patch applied for this.

Re: [HACKERS] self-deadlock at FATAL exit of boostrap process on read error

2006-06-07 Thread Qingqing Zhou
"Tom Lane" <[EMAIL PROTECTED]> wrote > > Do you have a test case to reproduce this problem? > According to the error message, the problem happens during reading pg_database. I just tried to plug in this line in mdread(): +/* pretend there is an error reading pg_database */ +if (r

Re: [HACKERS] self-deadlock at FATAL exit of boostrap process on read error

2006-06-07 Thread Tom Lane
"Qingqing Zhou" <[EMAIL PROTECTED]> writes: > I encounter a situation that the server can't shutdown when a boostrap > process does ReadBuffer() but gets an read error. Hm, AtProcExit_Buffers is assuming that we've done AbortTransaction, but the WAL-replay process doesn't do that because it's not

[HACKERS] self-deadlock at FATAL exit of boostrap process on read error

2006-06-07 Thread Qingqing Zhou
I encounter a situation that the server can't shutdown when a boostrap process does ReadBuffer() but gets an read error. I guess the problem may be like this - the boostrap process can't read at line: smgrread(reln->rd_smgr, blockNum, (char *) bufBlock); So it does a FATAL exit and shmem_exit