Re: WARNING: concurrent insert in progress within table "resource"

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Robert Haas <robertmhaas(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-02-27 15:54:25
Message-ID: CAFj8pRC+Zd_8t=hdbNeWwWPGAxWQUxEJzpCG6a7P4V+TyZCkqQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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

>>
>> postgres=# select version();
>>                                                 version
>> ──────────────────────────────────────────────────────────────────────────────────────────────────────────
>>  PostgreSQL 9.2devel on i686-pc-linux-gnu, compiled by gcc (GCC) 4.5.1
>> 20100924 (Red Hat 4.5.1-4), 32-bit
>> (1 row)
>>
>> Regards
>>
>> Pavel
>
> That seems bad.  But can you provide any more details about how to reproduce it?
>
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Florian Weimer 2012-02-27 16:00:47 Re: [PATCH] Documentation: remove confusing paragraph about backslash escaping
Previous Message Tom Lane 2012-02-27 15:32:23 Re: [PATCH] Documentation: remove confusing paragraph about backslash escaping