Jeff,
Sorry for the delayed response. Please see (some) answers inline.
On 12/1/2011 9:06 AM, Jeff Janes wrote:
> On Wed, Nov 30, 2011 at 7:27 AM, Benjamin Johnson
> wrote:
>> Experts,
>>
>> Quick Summary: data can now be inserted very quickly via COPY + removing
>> indexes, but is there a desi
Hello,
Can you find some relation between the memory usage and insert statements?
9.1.2 has memory problems with inserts (even the simplest ones) on Linux
and Windows too, I could produce it. Using pgbench also shows it. Some
memory is not reclaimed.
I could produce it also with 8.4.9 on Linux, I
Scott Marlowe wrote:
> On Wed, Dec 21, 2011 at 10:50 AM, Rafael Martinez
> wrote:
>> As long as I know, all the databases are using the default, "read
>> committed".
>
> Note that backups run in serializable mode.
In 9.1 they default to running in "repeatable read". You can choose
the --seria
On Wed, Dec 21, 2011 at 10:50 AM, Rafael Martinez
wrote:
> As long as I know, all the databases are using the default, "read
> committed".
Note that backups run in serializable mode.
--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscripti
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/21/2011 12:48 AM, Craig Ringer wrote:
> On 19/12/2011 11:04 PM, Rafael Martinez wrote:
>> Any ideas about why this dramatic change in memory usage when the only
>> thing apparently changed from our side is the postgres version?
>>
> It'd be inter
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 12/20/2011 12:15 PM, Cédric Villemain wrote:
> Le 19 décembre 2011 16:04, Rafael Martinez a écrit
> :
>> -BEGIN PGP SIGNED MESSAGE-
>> Hash: SHA1
>>
>> Hello
>>
>> I am sending this email to ask if anyone has noticed a change in how
>> a s
