Re: [Review] Include detailed information about a row failing a CHECK constraint into the error message
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Jan Kundrát <jkt@flaska.net>
Cc: Royce Ausburn <royce.ml@inomial.com>, Pg Hackers <pgsql-hackers@postgresql.org>
Date: 2011-11-21T14:52:56Z
Lists: pgsql-hackers
Commits
Same data as JSON:
GET /api/v1/messages/:b64id/commits
the thread's linked commits as JSON, with link sources.
API reference →
-
Don't assume that a tuple's header size is unchanged during toasting.
- b07b2bdc570c 9.0.6 cited
=?UTF-8?B?SmFuIEt1bmRyw6F0?= <jkt@flaska.net> writes: > On 11/16/11 23:13, Royce Ausburn wrote: >> Another super minor thing, postgres doesn't seem to put periods at the >> end of log messages, yet this new detail line does. > Again, I'm not familiar with the correct procedure. Shall I send a > revised patch for this one? Please read the message style guide (we do have one) http://developer.postgresql.org/pgdocs/postgres/error-style-guide.html regards, tom lane