Hi all With RAISE supporting user-defined SQLSTATEs, and EXCEPTION ... WHEN supporting matching them, shouldn't we explicitly declare a range of SQLSTATEs as reserved for custom use? Right now, there's nothing in http://www.postgresql.org/docs/current/static/errcodes-appendix.html to tell a user which SQLSTATE codes they can use without any risk that PostgreSQL will later use that code for something else. -- Craig Ringer http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Training & Services -- Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general