Re: Continuous archiving fails - Mailing list pgsql-bugs

From Tom Lane
Subject Re: Continuous archiving fails
Date
Msg-id 22113.1176390340@sss.pgh.pa.us
Whole thread Raw
In response to Continuous archiving fails  (David Darville <ml@darville.vm.bytemark.co.uk>)
Responses Re: Continuous archiving fails
List pgsql-bugs
David Darville <ml@darville.vm.bytemark.co.uk> writes:
> While testing a continuous archiving setup using PostgreSQL 8.2.3, on Debian
> Etch amd64, I found out that the slave database crashed when I did a 'DROP
> DATABASE' on the master.

Thanks for the report.  I believe this will fix it:

Index: dbcommands.c
===================================================================
RCS file: /cvsroot/pgsql/src/backend/commands/dbcommands.c,v
retrieving revision 1.187.2.1
diff -c -r1.187.2.1 dbcommands.c
*** dbcommands.c    27 Jan 2007 20:15:47 -0000    1.187.2.1
--- dbcommands.c    12 Apr 2007 14:40:40 -0000
***************
*** 1438,1443 ****
--- 1438,1446 ----
          /* Also, clean out any entries in the shared free space map */
          FreeSpaceMapForgetDatabase(xlrec->db_id);

+         /* Also, clean out any fsync requests that might be pending in md.c */
+         ForgetDatabaseFsyncRequests(xlrec->db_id);
+
          /* Clean out the xlog relcache too */
          XLogDropDatabase(xlrec->db_id);



            regards, tom lane

pgsql-bugs by date:

Previous
From: David Darville
Date:
Subject: Continuous archiving fails
Next
From: "Chris Fischer"
Date:
Subject: Problem identifying constraints which should not be inherited