Well, they are actually streaming replication slaves, and I boogered
up the rsync command, so there they are. I diffed the directories
from the master to the slave, and think I will go ahead and delete all
the files that don't appear in both places and see what happens.
Worst case, I have to set t
On 10/20/11 12:14 PM, Karsten Hilbert wrote:
Well, Ian isn't talking about removing data. What he was
asking (I believe) is how to remove from the data directory
files which got nothing to do with the database in question
(but probably look like database files because, say, someone
copied*another
On Thu, Oct 20, 2011 at 02:32:18PM -0400, Scott Mead wrote:
> On Thu, Oct 20, 2011 at 1:12 PM, Ian Harding wrote:
>
> > If someone happened to accidentally end up with a lot of files that
> > were NOT part of their database in the data/base/X directory, how
> > could they go about getting a
On Thu, Oct 20, 2011 at 1:12 PM, Ian Harding wrote:
> If someone happened to accidentally end up with a lot of files that
> were NOT part of their database in the data/base/X directory, how
> could they go about getting a reliable list of files they could safely
> delete? The files were ther
If someone happened to accidentally end up with a lot of files that
were NOT part of their database in the data/base/X directory, how
could they go about getting a reliable list of files they could safely
delete? The files were there before the current incarnation of the
database, so have ctim
