AW: [HACKERS] Caution: tonight's commits force initdb - Mailing list pgsql-hackers

From Zeugswetter Andreas IZ5
Subject AW: [HACKERS] Caution: tonight's commits force initdb
Date
Msg-id 219F68D65015D011A8E000006F8590C60339E0A6@sdexcsrv1.f000.d0188.sd.spardat.at
Whole thread Raw
Responses RE: [HACKERS] Caution: tonight's commits force initdb
List pgsql-hackers
> Hmm,Index scan is chosen to select all rows.
> AFAIK,sequential scan + sort is much faster than index scan in
> most cases.
> 
>     cost of index scan < cost of sequential scan + cost of sort
> 
This is usually true. It might need resources though that are not available,
e.g. 8 GB sort space. It also depends on whether the application is
interested in
first row (interactive), or all row performance (batch). Other DB's can
switch modes 
to decide on the wanted behavior. So I think there is no yes/no decision on
this.

Andreas


pgsql-hackers by date:

Previous
From: "Ansley, Michael"
Date:
Subject: Lex and things...
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: [HACKERS] Caution: tonight's commits force initdb