<div dir="ltr"><div class="gmail_default" style="font-family:georgia,serif;color:rgb(0,0,0)">Jaime,<br><br></div><div class="gmail_default" style="font-family:georgia,serif;color:rgb(0,0,0)">For saving space you can use syslog and keep the logs on different machine. Create the log hourly basis like log-00, log-01 and gzip them after being written to. That will save space. <br>
</div></div><div class="gmail_extra"><br clear="all"><div><div dir="ltr"><div><span style="color:rgb(68,68,68)"><font face="georgia,serif">Regards,<br></font></span></div><font face="georgia,serif"><span style="color:rgb(68,68,68)">Granthana</span><br>
</font></div></div>
<br><br><div class="gmail_quote">On Wed, Feb 12, 2014 at 4:43 AM, Jaime Casanova <span dir="ltr"><<a href="mailto:jaime@2ndquadrant.com" target="_blank">jaime@2ndquadrant.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="">On Tue, Feb 11, 2014 at 1:41 AM, Granthana Biswas <<a href="mailto:granthana@zedo.com">granthana@zedo.com</a>> wrote:<br>
> Jaime,<br>
><br>
> You can setup Pgbadger for master and slave database which will show the<br>
> number of SELECT and DML queries being fired for a day on both. You can get<br>
> the ratio from that. Logging in database should be set for all the queries.<br>
><br>
<br>
</div>yeah i thought on that the bad thing is that it could take a lot of<br>
space because of logs... the other option i was thinking was using<br>
pg_stat_statements and take snapshots every often... it's less<br>
accurate but maybe it use less space too.<br>
<br>
i think that is an important info pgpool should capture and display easily<br>
<div class="HOEnZb"><div class="h5"><br>
--<br>
Jaime Casanova <a href="http://www.2ndQuadrant.com" target="_blank">www.2ndQuadrant.com</a><br>
Professional PostgreSQL: Soporte 24x7 y capacitación<br>
Phone: +593 4 5107566 Cell: +593 987171157<br>
</div></div></blockquote></div><br></div>