Re: Cost Model

2017-12-20 Thread neto brpr
2017-12-20 17:34 GMT-02:00 Andres Freund : > On 2017-12-20 17:13:31 -0200, neto brpr wrote: > > Just to explain it better. The idea of ​​differentiating read and write > > parameters (sequential and random) is exactly so that the access plans > can > > be better chosen b

Re: Cost Model

2017-12-20 Thread neto brpr
2017-12-20 16:37 GMT-02:00 David G. Johnston : > On Wed, Dec 20, 2017 at 11:26 AM, neto brpr wrote: > >> Dear David >> I have read documentation that you send, but it has only sequential page >> cost and random page cost parameters. What I need, would be a model of &g

Re: Cost Model

2017-12-20 Thread neto brpr
2017-12-20 16:35 GMT-02:00 Alvaro Herrera : > neto brpr wrote: > > Dear David > > I have read documentation that you send, but it has only sequential page > > cost and random page cost parameters. What I need, would be a model of > > custo for Differentiate Read/W

Re: Cost Model

2017-12-20 Thread neto brpr
. Johnston : > On Wed, Dec 20, 2017 at 10:29 AM, neto brpr wrote: > >> Any comment, hint about it or something, please inform me. >> > > The docs contain this - its seem to cover what you describe: > > ​https://www.postgresql.org/docs/10/static/runtime-config- > query.html#RUNTIME-CONFIG-QUERY-CONSTANTS > > David J. > >

Cost Model

2017-12-20 Thread neto brpr
Hello All Anyone know if there is a patch that changes the PostgreSQL cost model in some way? I'm working with an tuning technique, based in hybrid storage environments (HDDs and SSDs). I need to know if exist any patches that allow postgresql to differentiate, for example, I/O costs of read and