From: "Alvaro Herrera" <alvhe...@2ndquadrant.com>
There was also the idea that this would be driven off SQLSTATE but this
seems pretty unwieldy to me.
You are referring to this long discussion, don't you?
http://www.postgresql.org/message-id/19791.1335902...@sss.pgh.pa.us
I've read it before, and liked the SQLSTATE-based approach. It seems like
properly assigned SQLSTATEs can be used as message IDs, and pairs of
SQLSTATE and its user action might be utilized to provide sophisticated
database administration GUI.
That discussion sounds interesting, and I want to take more time to
consider. But what do you think of my original suggestion to easily solve
the current issue? I'd like to remove the current annoying problem first
before spending much time for more excited infrastructure.
Regards
MauMau
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
