>>> 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. >> 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. > It leads me to another question. How could we *really* change the pgpool > settings permanently (in the postgresql fashion for user, database or > user+database) from SQL commands ? > > Shouldn't we *require* PostgreSQL installed on the pooler server to be > able to store some pgpool settings that would overwrite the settings > from config files ? Having it in a file is may be an idea but I don't want to have PostgreSQL installation just for storing pgpool settings. Sounds like overkill. -- Tatsuo Ishii SRA OSS, Inc. Japan English: http://www.sraoss.co.jp/index_en.php Japanese: http://www.sraoss.co.jp _______________________________________________ Pgpool-hackers mailing list Pgpool-hackers@pgfoundry.org http://pgfoundry.org/mailman/listinfo/pgpool-hackers
