Re: about some parameters - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: about some parameters
Date
Msg-id 3073cc9b1001022300m4cd0b826i7f4e79b2a81b7b26@mail.gmail.com
Whole thread Raw
In response to Re: about some parameters  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On Fri, Jan 1, 2010 at 12:21 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>
>> another parameter that is interesting is seq_page_cost, AFAIUI all the
>> other cost parameters (in the planner section of course) are relative
>> to this one. so what is the logic in allow changing it?
>
> Please read the discussions that went on when we added that parameter.
>

digging the archives is alway an interesting sport, from this one i
have learnt some things:

1) now i know was the meaning of GUC: Grand Unified Config (one mistery less)
2) that seq_page_cost was added when i was around here but apparently
not looking
3) seems like the idea of this GUC started as a multiplier for all
*_cost parameters but ended being just for random_page_cost
4) ... and that Tom has three hands
(http://archives.postgresql.org/pgsql-hackers/2006-05/msg01346.php)

--
Atentamente,
Jaime Casanova
Soporte y capacitación de PostgreSQL
Asesoría y desarrollo de sistemas
Guayaquil - Ecuador
Cel. +59387171157


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: So do we really *need* those substring() ops in tab-completion queries?
Next
From: Martijn van Oosterhout
Date:
Subject: Re: So do we really *need* those substring() ops in tab-completion queries?