pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Amit Kapila <amit.kapila16@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: Julien Rouhaud <rjuju123@gmail.com>
Cc: Kuntal Ghosh <kuntalghosh.2007@gmail.com>
Cc: Fujii Masao <masao.fujii@oss.nttdata.com>
Cc: Kirill Bychik <kirill.bychik@gmail.com>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Cc: Thomas Munro <thomas.munro@gmail.com>
Subject: Re: WAL usage calculation patch
Date: Mon, 6 Apr 2020 17:01:30 +0200
Message-ID: <ef8c966f-e50a-c583-7b1e-85de6f4ca0d3@2ndquadrant.com> (raw)
In-Reply-To: <CAA4eK1KqiWqAgw9ETchcQf-z9ZY4aUN-4QvTh0R26+DpNnTDHg@mail.gmail.com>
References: <20200330124356.GE79261@nol>
	<CAGz5QC+H4idCkRNojT0=VDLYs7mRBM0an6OZwS5NBdbrb6yKJA@mail.gmail.com>
	<20200401080152.GA82418@nol>
	<CAA4eK1KxT5ckuaiQqhUsNn=S3yQsxgC5aeiUoXxnS-i2W4K+_g@mail.gmail.com>
	<20200401142954.GA64485@nol>
	<CAA4eK1JULzGi9SrCnnPbKKiLaVnPhU+uUbbghduRNnC-zFeKAQ@mail.gmail.com>
	<20200402083035.GB64485@nol>
	<CAA4eK1+CDwmKyJeDYHZ4xFftK9TRW5pF+kkPsgGY8UAJqFNJKQ@mail.gmail.com>
	<20200402124818.GD64485@nol>
	<CAA4eK1LNg7Q6pxrochATMSJmadrzPKJODGAAxbgmgnWbi63UNw@mail.gmail.com>
	<CAFiTN-sHQ-bHwqEYOVOMjZ7VoQafWKLaTYiWvf-rR+twZ4LOwQ@mail.gmail.com>
	<CAFiTN-sONFPUHxMpn9m4=Z+m_MubCdvcVD75+QRK5jxVmUce8w@mail.gmail.com>
	<CAA4eK1LjkwGOegWMfs3tggD3-BXLzyZXFz7qBZaf_yLBPjZdHQ@mail.gmail.com>
	<CAFiTN-su_D35-csorD=soxnkL=g9ZVdnTN3QfPfK_TNp2t4Kug@mail.gmail.com>
	<CAFiTN-vAqkDV5Whxw2OvdbN9OU7xZyKzRrUG6m6dr8nvG-R=Yw@mail.gmail.com>
	<CAA4eK1Jh=EjwK+etqeaWM6gcNaex1FX6xTFqR7QXXQy2CmGQsw@mail.gmail.com>
	<CAA4eK1KqiWqAgw9ETchcQf-z9ZY4aUN-4QvTh0R26+DpNnTDHg@mail.gmail.com>

I noticed in some of the screenshots that were tweeted that for example in

     WAL:  records=1  bytes=56

there are two spaces between pieces of data.  This doesn't match the 
rest of the EXPLAIN output.  Can that be adjusted?

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services





view thread (130+ messages)  latest in thread

Message-ID: <ef8c966f-e50a-c583-7b1e-85de6f4ca0d3@2ndquadrant.com>
Permalink:  ../ef8c966f-e50a-c583-7b1e-85de6f4ca0d3@2ndquadrant.com/
Also on:    postgresql.org/message-id/ef8c966f-e50a-c583-7b1e-85de6f4ca0d3@2ndquadrant.com

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: peter.eisentraut@2ndquadrant.com, amit.kapila16@gmail.com, dilipbalaut@gmail.com, rjuju123@gmail.com, kuntalghosh.2007@gmail.com, masao.fujii@oss.nttdata.com, kirill.bychik@gmail.com, thomas.munro@gmail.com
  Subject: Re: WAL usage calculation patch
  In-Reply-To: <ef8c966f-e50a-c583-7b1e-85de6f4ca0d3@2ndquadrant.com>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox