From: Bendik R.Johansen <bendik.johansen@gmail.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: PostgreSQL Perform <pgsql-performance@postgresql.org>
Subject: Re: Slow update
Date: Tue, 12 Apr 2005 17:37:42 +0200
Message-ID: <9e217f24329eaf693ab6921123213178@gmail.com> (raw)
In-Reply-To: <16172.1113319006@sss.pgh.pa.us>
References: <0201deb23790cee173bdd2d3f0e96642@gmail.com>
<15725.1113316540@sss.pgh.pa.us>
<4bbbc6d3a436e415be630d768d609ef6@gmail.com>
<16172.1113319006@sss.pgh.pa.us>
Yes, I tried dropping it but it did not make a difference.
Could the table be corrupt or something?
Well, the important thing is that I now know that this is not typical
for PostgreSQL, so I will not have to rethink my whole project.
Thanks, so far.
On Apr 12, 2005, at 17:16, Tom Lane wrote:
> "Bendik R. Johansen" <bendik.johansen@gmail.com> writes:
>> Below is the schema for the table i will be using. I tried dropping
>> the
>> index, but it did not help.
>
>> Indexes:
>> "records_pkey" PRIMARY KEY, btree (id)
>> "records_category_idx" gist (category)
>> "records_cid_idx" btree (cid)
>> "records_uid_idx" btree (uid)
>
> Hmm ... my suspicion would fall first on the GIST index, to tell you
> the
> truth. Did you try dropping that one?
>
> regards, tom lane
>
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: bendik.johansen@gmail.com, tgl@sss.pgh.pa.us
Subject: Re: Slow update
In-Reply-To: <9e217f24329eaf693ab6921123213178@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox