Dan Ports <drkp(at)csail(dot)mit(dot)edu> wrote:
 
> I am surprised to see that error message without SSI's hint about
> increasing max_predicate_locks_per_xact.
 
After reviewing this, I think something along the following lines
might be needed, for a start.  I'm not sure the Asserts are actually
needed; they basically are checking that the current behavior of
hash_search doesn't change.
 
I'm still looking at whether it's sane to try to issue a warning
when an HTAB exceeds the number of entries declared as its max_size
when it was created.
 
-Kevin

In response to

• Re: SSI bug? at 2011-03-18 18:18:32 from Dan Ports

Responses

• Re: SSI bug? at 2011-03-18 21:57:32 from Kevin Grittner
• Re: SSI bug? at 2011-03-25 19:23:14 from Robert Haas

pgsql-hackers by date

Next:	From: Aidan Van Dyk	Date: 2011-03-18 21:08:11
	Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.
Previous:	From: Markus Wanner	Date: 2011-03-18 19:41:00
	Subject: Re: Re: [COMMITTERS] pgsql: Efficient transaction-controlled synchronous replication.