[Pgpool-hackers] show pool_status like...

[Guillaume Lelarge]

On Fri, 2011-09-16 at 08:02 +0900, Tatsuo Ishii wrote:
> > On Thu, 2011-09-15 at 07:57 +0900, Tatsuo Ishii wrote:
> >> >>> Hi,
> >> >>>
> >> >>> While I took a look at MySQL manual (mainly for checking query cache
> >> >>> functionality), I noticed that MySQL has following syntx:
> >> >>>
> >> >>> show .... like 'foo%';
> >> >>>
> >> >>> I think this is usefull for "show pool_status" command since it has
> >> >>> lengthy output now.
> >> >>>
> >> >>> Usage of show pool_status and like will be something like:
> >> >>>
> >> >>> show pool_status like 'client_idle%' will only show the status of
> >> >>> client_idle_limit and client_idle_limit_in_recovery.
> >> > 
> >> > Did you read our answer from Guillaume Lelarge and me ?
> >> > 
> >> > I would rather push forward pgpool_adm which is much more cleaner in
> >> > many aspects and remove SHOW commands all together.
> >> 
> >> I don't agree removing show commands. At least until the day when
> >> pgpool_adm functions are popular enough among users.
> >> 
> > 
> > Neither do I.
> > 
> >> >> In the mean time, I also thinking about "SET" command for
> >> >> pgpool-II. This would be usefull for change pgpool-II setting just for
> >> >> the session scope.
> >> 
> >> > What kind of parameters you would like to change for your session only ?
> >> 
> >> Lots. For example logging paramters, such as debug_level.  Also I
> >> would like to be able to change on memory query parameters on the fly.
> >> 
> > 
> > I would also like such a feature. But not with a SET command. Something
> > like a pgpool_set_option() stored function would please me more.
> 
> How do you implement it? Pcp process does not know anything about
> session local variables in pgpool child process.

Oh, you want it to be session only. I suppose I should have guessed.
What I don't understand is which setting would be interesting to set on
a session basis.


-- 
Guillaume
  http://blog.guillaume.lelarge.info
  http://www.dalibo.com