Re: WARNING: concurrent insert in progress within table "resource" - Mailing list pgsql-hackers

From Robert Haas
Subject Re: WARNING: concurrent insert in progress within table "resource"
Date
Msg-id CA+TgmoZFX-_CWJQ+UfW31D0_2pnziirhpJuLr6bXoUFFKWHE4w@mail.gmail.com
Whole thread Raw
In response to Re: WARNING: concurrent insert in progress within table "resource"  (Pavel Stehule <pavel.stehule@gmail.com>)
Responses Re: WARNING: concurrent insert in progress within table "resource"  (Pavel Stehule <pavel.stehule@gmail.com>)
List pgsql-hackers
On Mon, Feb 27, 2012 at 10:54 AM, Pavel Stehule <pavel.stehule@gmail.com> wrote:
> yes
>
> 2012/2/27 Robert Haas <robertmhaas@gmail.com>:
>> On Sun, Feb 26, 2012 at 10:04 AM, Pavel Stehule <pavel.stehule@gmail.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


pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: pgsql_fdw, FDW for PostgreSQL server
Next
From: Peter Eisentraut
Date:
Subject: Re: Fix PL/Python metadata when there is no result