From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: WARNING: concurrent insert in progress within table "resource" |
Date: | 2012-03-07 20:44:58 |
Message-ID: | CA+TgmoZFX-_CWJQ+UfW31D0_2pnziirhpJuLr6bXoUFFKWHE4w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, Feb 27, 2012 at 10:54 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
> yes
>
> 2012/2/27 Robert Haas <robertmhaas(at)gmail(dot)com>:
>> On Sun, Feb 26, 2012 at 10:04 AM, Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> wrote:
>>> Hello
>>>
>>> I tested creating some larger indexes
>>>
>>> There was a warning:
>>>
>>> postgres=# CREATE INDEX idx_resource_name ON resource (name, tid);
>>> WARNING: Â concurrent insert in progress within table "resource"
>>>
>>> I am sure so there was only one active session - so this warning is strange.
>>>
>
> sure
>
> I tried generate data from
> http://archives.postgresql.org/pgsql-performance/2012-02/msg00210.php
> example
>
> I used pg from yesterday GIT repository
>
> and my configuration was
>
> shared buffers 500MB
> maintenance_work_mem 200MB
> wal_buffers 64MB
> checkpoint_segments 32
Is this repeatable?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-03-07 20:47:22 | Re: Fix PL/Python metadata when there is no result |
Previous Message | Peter Eisentraut | 2012-03-07 20:44:38 | Re: pgsql_fdw, FDW for PostgreSQL server |