"Shulgin, Oleksandr" <oleksandr.shul...@zalando.de> writes: > What I dislike about this POC is all the disruption in libpq, to be > honest.
Yeah, I don't much like that either. But I don't think we can avoid some refactoring there; as designed, conversion of an error message into user-visible form is too tightly tied to receipt of the message. > It would be much neater if we could form the verbose message every > time and let the client decide where to cut it. Maybe a bit "too clever" > would be to put a \0 char between short message and it's verbose > continuation. The client could then reach the verbose part like this > (assuming that libpq did put a verbose part there): msg + strlen(msg) + 1. Blech :-( Thinking about it, though, it seems to me that we could get away with always performing both styles of conversion and sticking both strings into the PGresult. That would eat a little more space but not much. Then we just need to add API to let the application get at both forms. regards, tom lane -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers