Re: [REVIEW] Re: Compression of full-page-writes

From: Rahila Syed <rahilasyed(dot)90(at)gmail(dot)com>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: [REVIEW] Re: Compression of full-page-writes
Date: 2014-12-05 14:10:16
Message-ID: 1417788616446-5829403.post@n5.nabble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

I attempted quick review and could not come up with much except this

+ /*
+ * Calculate the amount of FPI data in the record. Each backup block
+ * takes up BLCKSZ bytes, minus the "hole" length.
+ *
+ * XXX: We peek into xlogreader's private decoded backup blocks for the
+ * hole_length. It doesn't seem worth it to add an accessor macro for
+ * this.
+ */
+ fpi_len = 0;
+ for (block_id = 0; block_id <= record->max_block_id; block_id++)
+ {
+ if (XLogRecHasCompressedBlockImage(record, block_id))
+ fpi_len += BLCKSZ - record->blocks[block_id].compress_len;

IIUC, fpi_len in case of compressed block image should be

fpi_len = record->blocks[block_id].compress_len;

Thank you,
Rahila Syed

--
View this message in context: http://postgresql.nabble.com/Compression-of-full-page-writes-tp5769039p5829403.html
Sent from the PostgreSQL - hackers mailing list archive at Nabble.com.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2014-12-05 14:28:13 Re: Review of GetUserId() Usage
Previous Message Heikki Linnakangas 2014-12-05 13:23:48 Re: compress method for spgist - 2