| Darcy Buskermolen 2006-02-03, 3:24 am |
| On Thursday 02 February 2006 17:27, jim- 2ZHQWDSZGnxeoWH0uzbU
5w@public.gmane.org wrote:
> Title: slonik doesn't catch errors properly
> Bug Type: Software bug
> Severity: Non-critical
> Software Version: Other
> Environment: FBSD 6.0, PGSQL 8.1
> Created By: decibel
> Description: slonik should catch the actual error causing this instead of
> only catching the invalid transaction:
>
> <stdin>:8: loading of file /usr/local/share/postgresql//slony1_funcs.sql:
> PGRES_FATAL_ERROR ERROR: current transaction is aborted,
> commands ignored until end of transaction block
> ERROR: current transaction is aborted, commands ignored until end of
> transaction block
>
> 17:36 < davidfetter> if you're not checking SQLSTATE (or other error code)
> after each attempted SQL statement, this is the kind of thing you see
This is not vialable way of testing in all versions of PG we support, does
any body else have any ideas?
>
>
> Note that in this case the error was due to trying to replicate to a
> machine running a different version of slony. Status: Submitted
>
>
>
> http://gborg.postgresql.org/project...update.php?1518
--
Darcy Buskermolen
Wavefire Technologies Corp.
http://www.wavefire.com
ph: 250.717.0200
fx: 250.763.1759
|