Re: SSI bug?
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
From: Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>
To: Kevin Grittner <Kevin.Grittner@wicourts.gov>
Cc: Dan Ports <drkp@csail.mit.edu>, YAMAMOTO Takashi <yamt@mwd.biglobe.ne.jp>, pgsql-hackers@postgresql.org
Date: 2011-04-11T08:38:30Z
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 →
-
Update key words table for 9.1
- bf6848bc8c82 9.1.0 cited
-
Documented some ecpg command line options that were missing:
- 71ac48fd9ceb 9.1.0 cited
On 11.04.2011 11:33, Heikki Linnakangas wrote: > I also noticed that there's a few hash_search(HASH_ENTER) calls in > predicate.c followed by check for a NULL result. But with HASH_ENTER, > hash_search never returns NULL, it throws an "out of shared memory" > error internally. I changed those calls to use HASH_ENTER_NULL, so you > now get the intended error message with the hint to raise > max_pred_locks_per_transaction. Oops, those were already fixed. Never mind. -- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com