Fixed issue of "drop table" scripts causing tests to fail in samples. Only done for sqlfire and postgres.

I believe others that do not have the "if exists" statements in their drop tables scripts should be retested as
I have not had to do this on any other previous version.  Suspect that "continueOnError" default flag has somehow
gotten flipped.

spring-batch-samples/src/main/resources/batch-postgresql.properties

@@ -0,0 +1,20 @@
+# Placeholders batch.*
+#    for Postgres:
+batch.jdbc.driver=org.postgresql.Driver
+batch.jdbc.url=jdbc:postgresql://localhost/samples
+batch.jdbc.user=postgres
+batch.jdbc.password=dba
+batch.jdbc.testWhileIdle=false
+batch.jdbc.validationQuery=
+batch.jdbc.verifyCursorPosition=false
+batch.drop.script=classpath:/org/springframework/batch/core/schema-drop-postgresql.sql
+batch.schema.script=classpath:/org/springframework/batch/core/schema-postgresql.sql
+batch.business.schema.script=business-schema-postgresql.sql
+batch.data.source.init=true
+batch.database.incrementer.class=org.springframework.jdbc.support.incrementer.PostgreSQLSequenceMaxValueIncrementer
+batch.database.incrementer.parent=sequenceIncrementerParent
+batch.lob.handler.class=org.springframework.jdbc.support.lob.DefaultLobHandler
+batch.grid.size=2
+batch.jdbc.pool.size=6
+batch.verify.cursor.position=false
+batch.isolationlevel=ISOLATION_SERIALIZABLE