[Pgpool-general] Suggestion for load_balancing mode

[Tatsuo Ishii]

> Tatsuo,
> 
> While debugging our pgpool installation it occurred to me that there's one 
> more kind of statement which ought to be load-balanced:
> CREATE TEMPORARY TABLE
> 
> As far as I can see, there is no reason why a temp table should be written to 
> both back-ends.  Of course, this will mean even more debugging on the backend 
> sync issue, but it seems like the right path to pursue.

But subsequent SELECT to the temporay table will have problem since
there's no gurantee that the SELECT always runs on the same server
where the temporary table created, no?

> Another thing to think about might be adding some more commands to allow 
> direct control of how a statement is handled when running replicated = true, 
> load_balance_mode = true.  For example:
> 
> /*REPLICATE*/ : rest of statement is sent to both back-ends regardless of 
> content.

Right now you can get the same effect by using /*NO LOAD BALANCE*/.

> /*LOADBALANCE*/ : rest of statement is load-balanced regardless of contents

Sounds good idea. Let me think more.
--
Tatsuo Ishii

> -- 
> --Josh
> 
> Josh Berkus
> Aglio Database Solutions
> San Francisco
> _______________________________________________
> Pgpool-general mailing list
> Pgpool-general at pgfoundry.org
> http://pgfoundry.org/mailman/listinfo/pgpool-general
>