"Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
> Andrew Alcheyev <buddy(at)telenet(dot)ru> wrote:
>> Well, it does good and the backend hasn't crashed yet, but the
>> client is still experiencing query problems at some point (not
>> far, I guess, from where its backend would segfault without the
>> patch). This time it encounters the following error from the
>> ERROR: out of shared memory
>> HINT: You might need to increase max_pred_locks_per_transaction.
> I noticed that you are using prepared transactions. Do you have
> any lingering transactions prepared but not committed or rolled
> back? (You can look in pg_prepared_xacts, and see when they were
>> So what should I do? Do I need to increase
>> "max_pred_locks_per_transaction" in postgresql.conf?
> Maybe, but let's rule out other problems first.
Has this been resolved? Any details would be useful to us.
In response to
pgsql-bugs by date
|Next:||From: David Schnur||Date: 2012-01-17 21:46:50|
|Subject: Re: Repeatable crash in pg_dump (with -d2 info)|
|Previous:||From: Noah Misch||Date: 2012-01-17 18:23:36|
|Subject: Re: fatal flex error in guc-file.l kills the postmaster|