om
> CC: pgsql-performance@postgresql.org
> Subject: Re: [PERFORM] Planner doesn't take indexes into account
>
> On 05/28/2014 04:59 AM, Grzegorz Olszewski wrote:
>
> > There is about 500,000 rows and about 500 new rows each business day.
> >
> > About 96% of
On 05/28/2014 04:59 AM, Grzegorz Olszewski wrote:
There is about 500,000 rows and about 500 new rows each business day.
About 96% of rows meet given conditions, that is, count shoud be about
480,000.
Heikki is right on this. Indexes are not a magic secret sauce that are
always used simply be
On 05/28/2014 12:59 PM, Grzegorz Olszewski wrote:
random_page_cost = 4.0
seq_page_cost = 1.0
There is about 500,000 rows and about 500 new rows each business day.
About 96% of rows meet given conditions, that is, count shoud be about 480,000.
When such a large percentage of the rows match, a
x27;t take indexes into account
From: rumman...@gmail.com
To: grzegorz.olszew...@outlook.com
CC: pgsql-performance@postgresql.org
What is random_page_cost and seq_page_cost in your server?And how many rows
does the table have?
On Tue, May 27, 2014 at 2:09 PM, Grzegorz Olszewski
wrote:
H
What is random_page_cost and seq_page_cost in your server?
And how many rows does the table have?
On Tue, May 27, 2014 at 2:09 PM, Grzegorz Olszewski <
grzegorz.olszew...@outlook.com> wrote:
> Hi,
>
> I wonder why planner uses Seq Scan instead of Index Scan.
>
> Here is my table (partial):
> con
Hi,
I wonder why planner uses Seq Scan instead of Index Scan.
Here is my table (partial):
content.contents
-+-+-
id | bigint | niepusty do
