slonik_drop_table and slonik_drop_sequence no longer attempt to
return -1 on an error (invalid as a slonik exit code in 2.1)
(cherry picked from commit
394ffa960a71f2d0fdfaffb0f5e75fe70fe0d2d6)
Conflicts:
RELEASE
- Bug #247 :: slony_logshipper can now handle the TRUNCATE commands
- Bug #248 :: Log Shipping files will now use the sequence name directly instead of
a tracking table.
+- slonik_drop_table and slonik_drop_sequence no longer attempt to
+ return -1 on an error (invalid as a slonik exit code in 2.1)
+
** 2.1.0
** 2.1.0 RC 2
$slonik .= " SET DROP SEQUENCE (id = $SEQ_ID, origin = $SET_ORIGIN);\n";
$slonik .= " } on error {\n";
$slonik .= " echo 'Could not drop sequence $SEQ_ID for $CLUSTER_NAME!';\n";
-$slonik .= " exit -1;\n";
+$slonik .= " exit 1;\n";
$slonik .= " }\n";
run_slonik_script($slonik, 'DROP SEQUENCE');
$slonik .= " SET DROP TABLE (id = $TABLE_ID, origin = $SET_ORIGIN);\n";
$slonik .= " } on error {\n";
$slonik .= " echo 'Could not drop table $TABLE_ID for $CLUSTER_NAME!';\n";
-$slonik .= " exit -1;\n";
+$slonik .= " exit 1;\n";
$slonik .= " }\n";
run_slonik_script($slonik, 'DROP TABLE');