Re: Postgres 9.2 PITR testing to before DROP DATABASE ends up removing file system files

I tried that when I was testing .. if I stopped at the most recent insert/update/delete previous to the drop database (with telling it to include the change) it DIDN'T include the change (I assume because the commit timestamp was slightly after the transaction timestamp) .. and if I told it to stop a little later than that, it removed the files (because it got to the drop database statement and stopped before the commit, but still deleted the files). For some reason it ignored SELECT statements - I assume those are not actually written into the wal files, and that would be why.  But .. that's only a guess.  I'm not that educated with regard to the inner workings of Postgres..  :)