Re: [Pgpool-general] understanding backend_weight
Tatsuo Ishii wrote: Out of curiosity, how would be such values handled? backend_hostname0 = 'postgres1' backend_weight0 = 0 backend_hostname1 = 'postgres2' backend_weight1 = 1 backend_hostname1 = 'postgres3' backend_weight1 = 2 postgres1 should not get any reads. postgres2 should get 33,3(3)% reads. postgres2 should get 66,6(6)% reads. Is my reasoning correct? Yes. See select_load_balancing_node() in child.c for more details. OK, thanks for your help. -- Tomasz Chmielewski http://wpkg.org ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] understanding backend_weight
Tomasz Chmielewski wrote: Thanks. Out of curiosity, how would be such values handled? I made some typos wrt numbers -once again, corrected below: backend_hostname0 = 'postgres1' backend_weight0 = 0 backend_hostname1 = 'postgres2' backend_weight1 = 1 backend_hostname1 = 'postgres3' backend_weight2 = 2 postgres1 should not get any reads. postgres2 should get 33,3(3)% reads. postgres3 should get 66,6(6)% reads. ? -- Tomasz Chmielewski http://wpkg.org ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] understanding backend_weight
> Out of curiosity, how would be such values handled? > > backend_hostname0 = 'postgres1' > backend_weight0 = 0 > > backend_hostname1 = 'postgres2' > backend_weight1 = 1 > > backend_hostname1 = 'postgres3' > backend_weight1 = 2 > > > postgres1 should not get any reads. > postgres2 should get 33,3(3)% reads. > postgres2 should get 66,6(6)% reads. > > Is my reasoning correct? Yes. See select_load_balancing_node() in child.c for more details. -- Tatsuo Ishii SRA OSS, Inc. Japan ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] understanding backend_weight
Tatsuo Ishii wrote: How should I understand "backend_weight" config variable? For example, I have two postgres servers: "local" and "remote". I would like to execute all SELECT operations on the "local" server only / mostly. What backend_weight should I use? backend_hostname0 = 'local' backend_weight0 = 1 backend_hostname1 = 'remote' backend_weight1 = 0 This one. Thanks. Out of curiosity, how would be such values handled? backend_hostname0 = 'postgres1' backend_weight0 = 0 backend_hostname1 = 'postgres2' backend_weight1 = 1 backend_hostname1 = 'postgres3' backend_weight1 = 2 postgres1 should not get any reads. postgres2 should get 33,3(3)% reads. postgres2 should get 66,6(6)% reads. Is my reasoning correct? -- Tomasz Chmielewski http://wpkg.org ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
Re: [Pgpool-general] understanding backend_weight
> How should I understand "backend_weight" config variable? > > For example, I have two postgres servers: "local" and "remote". > > I would like to execute all SELECT operations on the "local" server only > / mostly. > > > What backend_weight should I use? > backend_hostname0 = 'local' > backend_weight0 = 1 > > backend_hostname1 = 'remote' > backend_weight1 = 0 This one. -- Tatsuo Ishii SRA OSS, Inc. Japan ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
[Pgpool-general] understanding backend_weight
How should I understand "backend_weight" config variable? For example, I have two postgres servers: "local" and "remote". I would like to execute all SELECT operations on the "local" server only / mostly. What backend_weight should I use? backend_hostname0 = 'local' backend_weight0 = 0 backend_hostname1 = 'remote' backend_weight1 = 1 Or maybe: backend_hostname0 = 'local' backend_weight0 = 1 backend_hostname1 = 'remote' backend_weight1 = 0 Or is the meaning of backend_weight totally different? -- Tomasz Chmielewski http://wpkg.org ___ Pgpool-general mailing list Pgpool-general@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-general
