[pgpool-hackers: 3437] Re: How to get node occupation and execution time from statements?

[Tatsuo Ishii]

>> > - A metric that calculates the utilization of pgpool, calculating a
>> > percentage using num_init_children max_pool
>>
>> Can be obainted from pcp_proc_info today.
>>
> 
> I tried this, but I need to put process by process to monitor all pool. I
> want a way to get info from all process in just one command, if it's
> possible...

Yes, try the -a option:

$ pcp_proc_info --help
pcp_proc_info - display a pgpool-II child process' information
Usage:
pcp_proc_info [OPTION...] [process-id]
Options:
  -U, --username=NAME    username for PCP authentication
  -h, --host=HOSTNAME    pgpool-II host
  -p, --port=PORT        PCP port number
  -w, --no-password      never prompt for password
  -W, --password         force password prompt (should happen automatically)
  -P, --process-id=PID   PID of the child process to get information for (optional)
  -a, --all              display all child processes and their available connection slots
  -d, --debug            enable debug message (optional)
  -v, --verbose          output verbose messages
  -?, --help             print this help

>> > and child_max_connections
>>
>> It's not available today, not terrybly hard to implement, though.
>>
> 
> Nice!
> 
> 
>>
>> > - A metric that show the query execution time
>>
>> It's not available today, not terrybly hard to implement, though.
>>
> 
> Nice!
> 
> 
>>
>> > - A metric that show the 'tps', like in pg_top. So I can monitor how many
>> > transactions has been executed in the pool to measure the efficiency
>>
>> It's not available today. Interesting question is, how do you define
>> tps (I guess you mean "query per second", rather than "transactions
>> per second" by tps) as it needs to define a duration of query
>> execution. "Tps" is essentially:
>>
>> number_of_queries_executed / duration
>>
> 
> Yes! Exactly this! With this I can monitor the throughput of the pgpool and
> compare with the nodes.
> 
> How can I help to dev/test this or any other features? I'm really willing
> to help improve this amazing tool!

Thanks for the offering!

We mostly follow PostgreSQL's way:

On pgpool-hackers mailing list:

1) Propose a design for a feature to start a discussion.

2) Propose a patch against git master branch.

3) Continue discussions/updating the patch until all agreed.

4) Once all agreed one of committers take care of your patch to merge
   into the master branch.

5) The new cool feature will appear in the next major release!

Best regards,
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese:http://www.sraoss.co.jp