fillfactor and cluster table vs ZFS copy-on-write - Mailing list pgsql-general

From Geoff Speicher
Subject fillfactor and cluster table vs ZFS copy-on-write
Date
Msg-id CACEYah1en0ATkZNm75WRYt2D-MpK-cxPkROnXOWV9L=gmVQZfg@mail.gmail.com
Whole thread Raw
Responses Re: fillfactor and cluster table vs ZFS copy-on-write  (Qingqing Zhou <zhouqq.postgres@gmail.com>)
List pgsql-general
I am trying to determine the behavior of a system using ZFS to back a PostgreSQL instance as it relates to fillfactor and table clustering.

ZFS implements copy-on-write, so when PostgreSQL modifies a block on disk, the filesystem writes a new block rather than updating the existing block. Unless I'm missing something, this would seem to negate the purpose of using any fillfactor less than 100% and reduce any benefits of using CLUSTER. In fact, when using ZFS snapshots, it would seem that CLUSTER would actually be wasteful.

Therefore one might posit that PostgreSQL should be configured to use 100% fillfactor and avoid clustering on ZFS. Can anyone comment on this?

Thanks,
Geoff

pgsql-general by date:

Previous
From: TonyS
Date:
Subject: Error using DAO with the ODBC driver S1000: positioned_load in pos_newload failed
Next
From: William Dunn
Date:
Subject: PL\pgSQL 'ERROR: invalid input syntax for type oid:' [PostgreSQL 9.3.6 and 9.4]