From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: confusing error message |
Date: | 2013-08-09 16:09:07 |
Message-ID: | 20130809160907.GZ2706@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
* Tom Lane (tgl(at)sss(dot)pgh(dot)pa(dot)us) wrote:
> This is all sufficiently bizarre that I don't know if there's an
> easy explanation.
It occurs to me that users, when faced with complex error messages, are
very likely to go to their favorite search engine with it and rarely
does that lead them to any documentation on the subject but instead they
get mailing list archives or q-and-a type of websites.
Perhaps we should add an area to our documentation which provides more
information about the specific error messages which PostgreSQL returns?
That's not a terribly exciting bit of documentation to write, but
perhaps it would be very useful for our users.
Thoughts?
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2013-08-09 16:23:59 | Re: BUG #8335: trim() un-document behaviour |
Previous Message | Noah Misch | 2013-08-09 15:08:52 | Re: mvcc catalo gsnapshots and TopTransactionContext |