Re: Terrible Write Performance of a Stored Procedure - Mailing list pgsql-performance

From Brian Troutwine
Subject Re: Terrible Write Performance of a Stored Procedure
Date
Msg-id 971980cc0906261335m7dde5496n2557f54eea4e6d8b@mail.gmail.com
Whole thread Raw
In response to Re: Terrible Write Performance of a Stored Procedure  (Alan Hodgson <ahodgson@simkin.ca>)
List pgsql-performance
> Indexes are good things. Try them. Particularly on the isbn field.

I'm not sure why amazon_items.isbn should be given an index.
item_details.isbn is used in a WHERE clause and is given an index
accordingly, but not amazon_items.isbn.

Brian



On Fri, Jun 26, 2009 at 12:40 PM, Alan Hodgson<ahodgson@simkin.ca> wrote:
> On Friday 26 June 2009, Brian Troutwine <goofyheadedpunk@gmail.com> wrote:
>>  CREATE TABLE amazon_items (
>>         asin         char(10) PRIMARY KEY,
>>         locale       varchar(10) NOT NULL DEFAULT 'US',
>>         currency_code char(3) DEFAULT 'USD',
>>         isbn         char(13),
>>         sales_rank   integer,
>>         offers       text,
>>         offer_pages  integer DEFAULT 10,
>>         offers_last_updated timestamp NOT NULL DEFAULT CURRENT_TIMESTAMP,
>>         UNIQUE (asin, locale)
>>  );
>>
>
> Indexes are good things. Try them. Particularly on the isbn field.
>
> --
> Overshoot = http://www.theoildrum.com/files/evoltuion_timeline.JPG
>
> --
> Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-performance
>

pgsql-performance by date:

Previous
From: Merlin Moncure
Date:
Subject: Re: Terrible Write Performance of a Stored Procedure
Next
From: Brian Troutwine
Date:
Subject: Re: Terrible Write Performance of a Stored Procedure