;
> *From:* francisco.figueiredo...@gmail.com [mailto:
> francisco.figueiredo...@gmail.com] *On Behalf Of *Francisco Figueiredo Jr.
> *Sent:* Friday, March 09, 2012 12:41 PM
> *To:* Randy Ficker
> *Cc:* Marti Raudsepp; pgsql-general@postgresql.org
> *Subject:* RE: [GENERAL] 9.1 causing &q
edo...@gmail.com] On Behalf Of Francisco Figueiredo Jr.
Sent: Friday, March 09, 2012 12:41 PM
To: Randy Ficker
Cc: Marti Raudsepp; pgsql-general@postgresql.org
Subject: RE: [GENERAL] 9.1 causing "out of shared memory" error and higher
serialization conflicts
Would you mind to fill a bug rep
h 09, 2012 10:36 AM
> *To:* Randy Ficker
> *Cc:* pgsql-general@postgresql.org; Marti Raudsepp
> *Subject:* Re: [GENERAL] 9.1 causing "out of shared memory" error and
> higher serialization conflicts
>
> ** **
>
>
> Thanks for the heads up.
>
&
, March 09, 2012 10:36 AM
To: Randy Ficker
Cc: pgsql-general@postgresql.org; Marti Raudsepp
Subject: Re: [GENERAL] 9.1 causing "out of shared memory" error and higher
serialization conflicts
Thanks for the heads up.
I'll fix that in Npgsql so it sends the correct isolation level
I'm
> going to fix this right away. Thanks for the reply!
>
> -Original Message-
> From: Marti Raudsepp [mailto:ma...@juffo.org]
> Sent: Friday, March 09, 2012 9:41 AM
> To: Randy Ficker
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] 9.1 cau
after all. I'm going to
fix this right away. Thanks for the reply!
-Original Message-
From: Marti Raudsepp [mailto:ma...@juffo.org]
Sent: Friday, March 09, 2012 9:41 AM
To: Randy Ficker
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] 9.1 causing "out of shared memory"
On Fri, Mar 9, 2012 at 19:16, Randy Ficker wrote:
> Most writing transactions are using the REPEATABLE READ isolation
> level (the SERIALIZABLE level is not used at all).
Are you 100% sure about this? A major thing that changed in 9.1 was
implementation for proper SERIALIZABLE isolation, which co
Hello,
I recently upgraded my production database from 8.4 to 9.1. Ever since the
upgrade, I'm seeing a ton of "out of shared memory" errors as well as a
drastically increased quantity of serialization conflicts ("could not
serialize access due to read/write dependencies among transactions" er
