If cstore_fdw can't access a file, it should error out on CREATE about cstore_fdw

[jberkus]

Actually, examing what happened above, the errors which happen on CREATE are being supressed. The actual issue was that I hadn't deleted the cstore_footer file. Since I got no error message about that, I didn't know what was wrong.

[jberkus]

I'd say that this is a bug, not an enhancement.

[ozgune]

I think we can fix this issue doing one or both of the following.

1/ During Create Foreign Table, check that we can access the underlying data file. Also check that we don't have an existing footer file. Either warn or error out in this case.
2/ Drop Foreign Table deletes the data and footer files. This way, a new create table statement doesn't access an existing footer file.

Ideally, we'd do both. Out of curiosity, @jberkus, how did you delete the c_statements.cstore data file?

[jberkus]

rm -f c_statements.cstore

I'd prefer a WARN, not an error, because I can imagine cases where I deliberately want to re-attach an existing cstore file as a new, or even duplicate, foreign table. Currently I can have the same cstore file attached as several different foriegn table names, and I can see uses for that functionality, so I wouldn't want it to become impossible in the future.

For the DROP FOREIGN TABLE case, please see the discussion on that issue; it's complicated.

[samay-sharma]

This issue has been resolved with cstore_fdw v1.1 release. cstore_fdw now errors out on CREATE if there is a problem accessing the specified file location.

Also, DROP FOREIGN TABLE now deletes the data and footer files, making it difficult to re-attach a previously created cstore file by mistake.