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-03-07 21:32:42 |
Message-ID: | CAFj8pRDgHLy9gHEcJDLe13858xjr+T2aBO765uJJVjekJOndtg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2012/3/7 Robert Haas <robertmhaas(at)gmail(dot)com>:
> 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?
>
I didn't repeated this test, but I'll check it tomorrow.
Pavel
> --
> Robert Haas
> EnterpriseDB: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2012-03-07 21:43:10 | Re: Fix PL/Python metadata when there is no result |
Previous Message | Pavel Stehule | 2012-03-07 21:28:42 | Re: poll: CHECK TRIGGER? |