(Yes, I know I'm not on the hackers list. Most interested parties should
get this directly anyway.)
Additionally the interface exposed by the JDBC driver lets the user
write arbitrary CopyData bytes to the server, so without parsing all of
that we don't know whether they've issued CopyData(EOF
The error on createdb happened again this morning. However, this time an
abandoned directory was not created. The full error message was:
$ createdb -E SQL_ASCII -U flyminebuild -h brian.flymine.org -T
production-flyminebuild production-flyminebuild:uniprot
createdb: database creation failed:
Heikki Linnakangas <[EMAIL PROTECTED]> writes:
Another thought is to ignore ENOENT in copydir.
On Wed, 8 Oct 2008, Tom Lane wrote:
Yeah, I thought about that too, but it seems extremely dangerous ...
I agree. If a file randomly goes missing, that's not an error to ignore,
even if you think
On Thu, 9 Oct 2008, Tom Lane wrote:
So I'm mystified
how Matthew could have seen the expected error and yet had the
destination tree (or at least large chunks of it) left behind.
Remember I was running 8.3.0, and you mentioned a few changes after that
version which would have made sure the des
