Re: [REVIEW] Re: Compression of full-page-writes - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: [REVIEW] Re: Compression of full-page-writes
Date
Msg-id 20141125134848.GD1639@alvin.alvh.no-ip.org
Whole thread Raw
In response to Re: [REVIEW] Re: Compression of full-page-writes  (Michael Paquier <michael.paquier@gmail.com>)
Responses Re: [REVIEW] Re: Compression of full-page-writes  (Michael Paquier <michael.paquier@gmail.com>)
List pgsql-hackers
Michael Paquier wrote:

> Exposing compression and decompression APIs of pglz makes possible its
> use by extensions and contrib modules. pglz_decompress contained a call
> to elog to emit an error message in case of corrupted data. This function
> is changed to return a boolean status to let its callers return an error
> instead.

I think pglz_compress belongs into src/common instead.  It
seems way too high-level for src/port.

Isn't a simple boolean return value too simple-minded?  Maybe an enum
would be more future-proof, as later you might want to add more values,
say distinguish between different forms of corruption, or fail due to
out of memory, whatever.

-- 
Álvaro Herrera                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services



pgsql-hackers by date:

Previous
From: Alex Shulgin
Date:
Subject: Re: Missing OOM checks in libpq (was Re: Replication connection URI?)
Next
From: Fujii Masao
Date:
Subject: Re: Add shutdown_at_recovery_target option to recovery.conf