Re: Shouldn't the planner have a higher cost for reverse index scans?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Lists <lists@xxxxxxxxxxx>
Subject: Re: Shouldn't the planner have a higher cost for reverse index scans?
From: Grzegorz Jaśkiewicz <gryzman@xxxxxxxxx>
Date: Thu, 16 Apr 2009 09:11:08 +0100
Cc: Josh Berkus <josh@xxxxxxxxxxxx>, Tom Lane <tgl@xxxxxxxxxxxxx>, postgres performance list <pgsql-performance@xxxxxxxxxxxxxx>
In-reply-to: <49E6C9F5.1050205@xxxxxxxxxxx>
References: <49DEEA75.3060008@xxxxxxxxxxxx> <21658.1239371437@xxxxxxxxxxxxx> <49DF7CE5.4020404@xxxxxxxxxxxx> <25703.1239383976@xxxxxxxxxxxxx> <49DF8603.3000006@xxxxxxxxxxxx> <49E6C9F5.1050205@xxxxxxxxxxx>

create index foobar on table(row desc);

-- 
Sent via pgsql-performance mailing list (pgsql-performance@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

References:
- Shouldn't the planner have a higher cost for reverse index scans?
  - From: Josh Berkus
- Re: Shouldn't the planner have a higher cost for reverse index scans?
  - From: Tom Lane
- Re: Shouldn't the planner have a higher cost for reverse index scans?
  - From: Josh Berkus
- Re: Shouldn't the planner have a higher cost for reverse index scans?
  - From: Tom Lane
- Re: Shouldn't the planner have a higher cost for reverse index scans?
  - From: Josh Berkus
- Re: Shouldn't the planner have a higher cost for reverse index scans?
  - From: Lists

Prev by Date: Re: Shouldn't the planner have a higher cost for reverse index scans?
Next by Date: Really dumb planner decision
Previous by thread: Re: Shouldn't the planner have a higher cost for reverse index scans?
Next by thread: Re: Shouldn't the planner have a higher cost for reverse index scans?
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]