Triggered by thread "Must the file be deleted after \"copy binary into table
from file\"" on July 19, 2013:
3) In case the copy into file, e.g., due to a failing sanity check after the
file is moved, that data is factually lost, i.e., the files are gone, but no
data is loaded into the database; we need to either document this clearly, or
make the implementation behave like a transaction.
For now, we should document this behaviour. But a long term solution is to implement the transactional behaviour.
Since files are no longer deleted by COPY BINARY INTO, is this still a problem?