Drop Down MenusCSS Drop Down MenuPure CSS Dropdown Menu

Pgbadger Feature In Postgresql

-
1. pgBadger reports everything about your SQL queries
           Overall statistics
           The most frequent waiting queries.
           Queries that waited the most.
           Queries generating the most temporary files.
           Queries generating the largest temporary files.
           The slowest queries.
           Queries that took up the most time.
           The most frequent queries.
           The most frequent errors.
           Histogram of query times.
           Histogram of sessions times.
           Users involved in top queries.
           Applications involved in top queries.
           Queries generating the most cancellation.
           Queries most cancelled.

  2. The following reports are also available with hourly charts divided into periods of five minutes:
            SQL queries statistics.
           Temporary file statistics.
           Checkpoints statistics.
           Autovacuum and autoanalyze statistics.
           Cancelled queries.
           Error events (panic, fatal, error and warning).

  3. There are also some pie charts about distribution of:
            Locks statistics.
           Queries by type (select/insert/update/delete).
           Distribution of queries type per database/application
           Sessions per database/user/client/application.
           Connections per database/user/client/application.
           Autovacuum and autoanalyze per table.
           Queries per user and total duration per user.

     All charts are zoomable and can be saved as PNG images. SQL queries
   reported are highlighted and beautified automatically.

  4. pgBadger is also able to parse pgbouncer log files and to create the
   following reports:
           Request Throughput
           Bytes I/O Throughput
           Queries Average duration
           Simultaneous sessions
           Histogram of sessions times
           Sessions per database
           Sessions per user
           Sessions per host
           Established connections
           Connections per database
           Connections per user
           Connections per host
           Most used reserved pools
           Most Frequent Errors/Events

     You can also have incremental reports with one report per day and a
   cumulative report per week. Two multiprocess modes are available to
   speed up log parsing, one using one core per log file, and the second
   using multiple cores to parse a single file. These modes can be
   combined.

     Histogram granularity can be adjusted using the -A command line option.
   By default they will report the mean of each top queries/errors occuring
   per hour, but you can specify the granularity down to the minute.

     pgBadger can also be used in a central place to parse remote log files
   using a passwordless SSH connection. This mode can be used with
   compressed files and in the multiprocess per file mode (-J) but can not
   be used with the CSV log format



Comments

Post a Comment

Popular posts from this blog

postgreSQL Compress format backup

-
The -F option on pg_dump allows you to specify the format of the output. The default output is plain-text. That’s what you get when you do this: pg_dump bacula > bacula.sql and is functionally equivalent to doing: pg_dump -Fp bacula > bacula.sql There are other formats (directory, tar), but today I’m concerned with the custom (c) option. By default, this output is also compressed (see the -Z option). What is of most value is the ability to use  pg_restore  with the custom output. What’s the big deal about custom format? The more interesting option on pg_restore was -j. This allows you to run multiple concurrent jobs for the loading of data and building of indexes. This can greatly reduce the amount of time needed to restore a large database if your server has multiple processors. pg_restore can be much more useful than just doing: psql bacula < bacula.sql With pg_restore you can be very selective about what you restore. See the -L and -l options. How much do
Read more

How to find the server is whether standby (slave) or primary(master) in Postgresql replication ?

-
Method 1 You can check the mode of the server using "pg_controldata". [pgsql@test~]$ pg_controldata /usr/local/pgsql/data84/ Database cluster state: in archive recovery --> This is Standby Database Database cluster state: in production --> This is Production Database [Master] Method 2 You can use pg_is_in_recovery() which returns True if recovery is still in progress(so the server is running in standby mode or slave) postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- t (1 row) If Return    false   so the server is running in primary mode or master postgres=# select pg_is_in_recovery(); pg_is_in_recovery ------------------- f (1 row)
Read more

Top 10 Highest Paying URL Shortener Companies - Best URL Shorteners To Earn Fast

-
Image
These are the lists of top paying url shortening websites that are similar to Adfoc.us or Shrink url Websites like Adfoc.us. The websites are similar in the sense that you can use the same pattern of registration and earnings for all them, but the only difference is the amount of money each pays to its members and also the percentage of earnings from their referral programs. 1. ADF.LY – Free Url Shortening similar to adfocus that will pay you $4 for 1000 clicks on your shorten url. You can Also refer your friends and earn 20% of their earnings for life. Their payment is quick and consistant. Paypal Or Alertpay. It’s legit and very popular. JOIN  HERE Payment Options Details :- Payout for 1000 Views: Upto $9 Minimum Payout: $5 Referral Commission: 20% Payment Options:Payoneer, Payza Payment Time : Daily and On Request You can Withdraw money Following Accounts:- 2. LINKBUCKS – free url shortening LINKBUCKS is a free url shortening service website si
Read more

7 Steps to configure BDR replication in postgresql

-
Image
 The  BDR  (Bi-Directional Replication) project adds multi-master replication to PostgreSQL 9.4.  Postgres-BDR has a lower impact on the masters(s) than trigger-based replication solutions. There is no write-amplification, as it does not require triggers to write to queue tables in order to replicate writes.   Here We are using  postgres version 9.4.12 and bdr version 1.0.2. for configuring  multi master replication . Simply Following 7 steps you can configure the multi master replication in postgresql. To download the bdr in below link. .   https://github.com/2ndQuadrant/bdr/archive/bdr-pg/REL9_4_12-1.tar.gz $ tar -xzvf REL9_4_12-1.tar.gz $ wget https://github.com/2ndQuadrant/bdr/archive/bdr-plugin/1.0.2.tar.gz $ tar -xzvf 1.0.2.tar.gz 1. To install BDR. $ cd ~/bdr-bdr-pg-REL9_4_12-1 $ ./configure --prefix=/usr/lib/postgresql/9.4 --enable-debug --with-openssl $ make -j4 -s install-world $ cd ~/bdr-bdr-plugin-1.0.2 $ PATH=/usr/lib/postgresql/9.4/bin:"$PATH" ./c
Read more

Postgres Streaming Replication Configuration

-
Primary - Existing Test Server: ======= Hostname: nijam-1 IP Address: 53.99.198.11 Secodary - New Test Server ======== Hostname: nijam-2 IP Address: 53.99.198.12 ===================================================== Step 1. stop the slave server /optt/10.5/bin/pg_ctl -D /DATA stop Step 2. move the slave data directory to backup location: mv /DATA/* /tmp/backup Step 3. change below parameter on master postgresql.conf & pg_hba.conf files . listen_addresses = 'localhost,53.99.198.11' wal_level = replica # minimal, replica, or logical archive_mode = on archive_command = 'cp %p /ARCHIVES/%f' max_wal_senders = 10 wal_keep_segments = 25 On pg_hba.conf: host replication postgres 53.99.198.12/24 trust host replication postgres 53.99.198.11/24 trust Step 4. Restart the master server: /optt/10.5/bin/pg_ctl -D /DATA restart Step 5. taking consistancy backup: psql -c "sele
Read more