>> - The error handling loop around load_block() suggests that you're >> expecting some reads to fail, which I guess is because you could be >> trying to read blocks from a relation that's been rewritten under a >> different relfilenode, or partially or entirely truncated. But I >> don't think it's very reasonable to just let ReadBufferWhatever() spew >> error messages into the log and hope users don't panic. People will >> expect an automatic prewarm solution to handle any such cases quietly, >> not bleat loudly in the log. I suspect that this error-trapping code >> isn't entirely correct, but there's not much point in fixing it; what >> we really need to do is get rid of it (somehow). > > [Need Reelook] -- Debug and check if block load fails what will happen.
Oops Sorry, this was for self-reference. It is fixed now -- Thanks and Regards Mithun C Y EnterpriseDB: http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
