Re: [Patch] Make block and file size for WAL and relations defined at cluster creation

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Remi Colinet <remi(dot)colinet(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [Patch] Make block and file size for WAL and relations defined at cluster creation
Date: 2018-01-03 21:04:50
Message-ID: CA+TgmoaWsQM3youf=vNwH2tdJXaSJN2GNb47HFmt-SqLZe-dBw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jan 3, 2018 at 3:43 PM, Remi Colinet <remi(dot)colinet(at)gmail(dot)com> wrote:
> Justifications are:

I think this is all missing the point. If varying the block size (or
whatever) is beneficial, then having it configurable at initdb is
clearly useful. But, as Andres says, you haven't submitted any
evidence that this is the case. You need to describe scenarios in
which (1) a non-default blocksize performs better and (2) there's no
reasonable way to obtain the same performance improvement without
changing the block size.

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Stephen Frost 2018-01-03 21:14:24 Re: CFM for January commitfest?
Previous Message Alvaro Herrera 2018-01-03 20:59:13 Re: [HACKERS] Proposal: Local indexes for partitioned table