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

Re: Continuous archiving fails

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: David Darville <ml(at)darville(dot)vm(dot)bytemark(dot)co(dot)uk>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: Continuous archiving fails
Date: 2007-04-12 15:05:40
Message-ID: 22113.1176390340@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-bugs
David Darville <ml(at)darville(dot)vm(dot)bytemark(dot)co(dot)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

In response to

Responses

pgsql-bugs by date

Next:From: Chris FischerDate: 2007-04-12 19:17:02
Subject: Problem identifying constraints which should not be inherited
Previous:From: David DarvilleDate: 2007-04-12 12:19:48
Subject: Continuous archiving fails

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