From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Timing problem in DROP TABLESPACE? |
Date: | 2008-11-06 14:01:01 |
Message-ID: | 1225980061.22256.17.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
I've run regression tests many, many times recently, usually in the form
of a looping installcheck, rather than just make check.
On a recent test the last command of the last test has failed:
DROP TABLESPACE testspace;
ERROR: tablespace "testspace" is not empty
The directory was confirmed as non-empty, though when running the
command again it worked successfully.
However, I've run it many times and it hasn't happened at all, so it's
sporadic and fairly rare. When I isolate just that test case in a tight
loop, I've seen no problems.
Now I'm not sure what causes that and although I am working on patches I
don't think I'm causing it myself. This error happens on the *master*,
not on the standby server.
Is there a timing problem? I see that we attempt to do a checkpoint to
clean up deleted files. Is that working? Is it ignoring certain
messages?
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2008-11-06 14:01:57 | Re: [PATCH] EnableDisableTrigger Cleanup & Questions |
Previous Message | Tom Lane | 2008-11-06 13:59:12 | Re: Inefficiency in InitIndexFreeSpaceMap |