Examples of valid lines: (blank lines are skipped)

5678: INSERT INTO "OneTable" (firstname, surname) VALUES ('bbb', 'BBB');
1234: INSERT INTO "OneTable" (firstname, surname) VALUES ('aaa', 'AAA'); INSERT INTO "OneTable" (firstname, surname) VALUES ('hhh', 'HHH'); INSERT INTO "OneTable" (firstname, surname) VALUES ('iii', 'III');
3333: INSERT INTO "OneTable" (firstname, surname) VALUES ('ccc', 'CCC');
asdf: INSERT INTO "OneTable" (firstname, surname) VALUES ('ddd', 'DDD');
111: INSERT INTO "OneTable" (firstname, surname) VALUES ('eee', 'EEE');

6: INSERT INTO "OneTable" (firstname, surname) VALUES ('fff', 'FFF');
99999999999: INSERT INTO "OneTable" (firstname, surname) VALUES ('ggg', 'GGG');
9999: INSERT INTO "OneTable" (firstname, surname) VALUES ('kkk', 'KKK');

Quick summary:
* everything before the first /: / is ignored (I sometimes use this space for tagging lines for grepping them later)
* everything after the first /: / needs to be valid SQL for your Postgresql server
* you may include several SQL statements per line, separated by semi-colons (;) -- lines may be as long as you like
* in fact, this is the only way to make sure that separate statements are grouped in the same JDBC transaction
* split your SQL statements across multiple files to take advantage of multi-threading -- different thread for each file
* the number of threads used in each run, i.e. the number of files processed in each run, is determined in settings.xml


