Re: [GENERAL] Concurrency problem building indexes

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Wes <wespvp(at)syntegra(dot)com>
Cc: "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, pgsql-hackers(at)postgresql(dot)org, "wes(dot)palmer(at)bt(dot)com" <wes(dot)palmer(at)bt(dot)com>
Subject: Re: [GENERAL] Concurrency problem building indexes
Date: 2006-04-25 07:18:06
Message-ID: 13641.1145949486@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

Wes <wespvp(at)syntegra(dot)com> writes:
> On 4/25/06 1:01 AM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>> Where do you want me to send it to?
>>
>> pgsql-bugs would be appropriate.

> It's not that small that I would want to post it to a list. Also, I think
> I've sanitized the data, but I wouldn't want to post it on a public list.

So invent some made-up data. I'd be seriously surprised if this
behavior has anything to do with the precise data being indexed.
Experiment around till you've got something you don't mind posting
that exhibits the behavior you see.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2006-04-25 07:20:30 Re: remove another version of postgreSQL
Previous Message Tom Lane 2006-04-25 07:15:23 Re: invalid memory alloc request size 1684370054

Browse pgsql-hackers by date

  From Date Subject
Next Message Gevik Babakhani 2006-04-25 08:12:35 Re: TODO Item: ACL_CONNECT
Previous Message Wes 2006-04-25 06:52:31 Re: [GENERAL] Concurrency problem building indexes