Re: SSI bug?

From: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>
To: Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>
Cc: Dan Ports <drkp(at)csail(dot)mit(dot)edu>, YAMAMOTO Takashi <yamt(at)mwd(dot)biglobe(dot)ne(dot)jp>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: SSI bug?
Date: 2011-04-11 08:38:30
Message-ID: 4DA2BE06.1060806@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

In response to

  • Re: SSI bug? at 2011-04-11 08:33:06 from Heikki Linnakangas

Browse pgsql-hackers by date

  From Date Subject
Next Message Tatsuo Ishii 2011-04-11 08:42:25 pgfoundry down?
Previous Message Heikki Linnakangas 2011-04-11 08:33:06 Re: SSI bug?