Roberto Grandi wrote
> Thanks Igor,
>
> this is a sufficient idea to take into account for upgrading to 9.x
> release.
> Thanks again.
There is no 9.x "release" - singular
A release designation requires both the first and second position.
8.4.x
9.0.x
9.1.x
9.2.x
9.3.x
An ".x" can be used in the third position if the patch-release is unknown or
should not be relevant - which it is when discussing major features such as
the "DO" statement but not as much when discussing bugs and such which very
well may have been identified/fixed by a patch release.
If you intended to mean 9.0 or higher it is generally better to state the
explicitly "9.0+" or equivalent.
Apologies if you already know all this and were just imprecise in your
writing but it is a misconception that some people have.
Also, note that the "Transaction is aborted" error message is annoying but
harmless. In some cases, such as when you construct and entire script to be
executed at-once, you do not care about flow control and you will either
commit or rollback at the end depending on whether the script succeeded or
failed. In those cases, which I've personally experienced, it would be nice
to be able to suppress the warning explicitly (but just that specific one) -
but alas that is not currently possible that I am aware.
David J.
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/Catch-exceptions-outside-function-tp5771398p5771489.html
Sent from the PostgreSQL - admin mailing list archive at Nabble.com.
