Re: Oops - BF:Mastodon just died - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Oops - BF:Mastodon just died
Date
Msg-id 6494.1201790862@sss.pgh.pa.us
Whole thread Raw
In response to Re: Oops - BF:Mastodon just died  (Andrew Dunstan <andrew@dunslane.net>)
Responses Re: Oops - BF:Mastodon just died
List pgsql-hackers
Andrew Dunstan <andrew@dunslane.net> writes:
>>> Agreed, but I suggest waiting till 8.4 is branched unless you are really
>>> sure about this addition.  We freeze for 8.3.0 in less than 24 hours.

> I am pretty damn sure it's OK. It's pretty low risk (change an unlink 
> call to a rename call) and even if it's broken as my fist version was, 
> it doesn't appear to break the build. It's working on the buildfarm. I 
> want it in so if we have problems with 8.3 we don't have to go through 
> the handstands I had to to find out what was broken.

After looking at the patch, my only question is how all those junk files
get cleaned up at "make clean".
        regards, tom lane


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Remove pg_dump -i option (was Re: Proposed patch: synchronized_scanning GUC variable)
Next
From: "Kevin Grittner"
Date:
Subject: Re: [PATCHES] Better default_statistics_target