On Fri, Jun 3, 2011 at 1:01 PM, Alvaro Herrera <alvhe...@commandprompt.com> wrote: > Excerpts from Robert Haas's message of vie jun 03 12:44:45 -0400 2011: >> On Wed, Jun 1, 2011 at 2:28 PM, Robert Haas <robertmh...@gmail.com> wrote: > >> > (4) It strikes me that it might be possible to address this problem a >> > bit more cleanly by allowing mdnblocks() and smgrnblocks() and >> > RelationGetNumberOfBlocksInFork() to take a boolean argument >> > indicating whether or not an error should be thrown if the underlying >> > physical file happens not to exist. When no error is to be signaled, >> > we simply return 0 when the main fork doesn't exist, rather than >> > throwing an error. >> >> If we don't want to gum this with the above-mentioned cruft, the other >> obvious alternative here is to do nothing, and live with the >> non-beauty of the resulting error message. > > Option 4 seems reasonable to me ... can you get rid of the dupe > smgrnblocks call simultaneously?
What dup smgrnblocks call? Patch along these lines attached. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
reject-unlogged-during-recovery-v2.patch
Description: Binary data
-- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
