Re: Report: race conditions in WAL replay routines - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Report: race conditions in WAL replay routines
Date
Msg-id 22689.1328553139@sss.pgh.pa.us
Whole thread Raw
In response to Re: Report: race conditions in WAL replay routines  (Simon Riggs <simon@2ndQuadrant.com>)
Responses Re: Report: race conditions in WAL replay routines
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> The existing errmsg of "tablespace is not empty" doesn't cover all
> reasons why tablespace was not removed.

Yeah, in fact that particular statement is really pretty bogus for the
replay case, because as the comment says we know that the tablespace
*is* empty so far as full-fledged database objects are concerned.

> The final message should have
> errmsg "tablespace not fully removed"
> errhint "you should resolve this manually if it causes further problems"

Planning to go with this:
                        errmsg("directories for tablespace %u could not be removed",
xlrec->ts_id),                       errhint("You can remove the directories manually if necessary.")));
 

I thought about an errdetail, but the preceding LOG entries from
destroy_tablespace_directories should provide the details reasonably
well.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: 16-bit page checksums for 9.2
Next
From: Bruce Momjian
Date:
Subject: Re: 16-bit page checksums for 9.2