Re: increasing the default WAL segment size

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: increasing the default WAL segment size
Date: 2016-08-25 03:32:00
Message-ID: 3697.1472095920@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> On Wed, Aug 24, 2016 at 10:33 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> ... but I think this is just folly. You'd have to do major amounts
>> of work to keep, eg, slave servers on the same page as the master
>> about what the segment size is.

> I said an initdb-time parameter, meaning not capable of being changed
> within the lifetime of the cluster. So I don't see how the slave
> servers would get out of sync?

The point is that that now becomes something to worry about. I do not
think I have to exhibit a live bug within five minutes' thought before
saying that it's a risk area. It's something that we simply have not
worried about before, and IME that generally means there's some squishy
things there.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Venkata B Nagothi 2016-08-25 03:38:19 Re: patch proposal
Previous Message Robert Haas 2016-08-25 03:30:18 Re: increasing the default WAL segment size