Re: Redesigning checkpoint_segments

From: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
To: Daniel Farina <daniel(at)heroku(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, Heikki Linnakangas <hlinnakangas(at)vmware(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Redesigning checkpoint_segments
Date: 2013-06-06 03:23:43
Message-ID: 51B000BF.6070100@commandprompt.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


On 06/05/2013 06:23 PM, Daniel Farina wrote:
>
> On Wed, Jun 5, 2013 at 6:00 PM, Joshua D. Drake <jd(at)commandprompt(dot)com> wrote:
>> I didn't see that proposal, link? Because the idea of slowing down
>> wal-writing sounds insane.
>
> It's not as insane as introducing an archiving gap, PANICing and
> crashing, or running this hunk o junk I wrote
> http://github.com/fdr/ratchet
>

Well certainly we shouldn't PANIC and crash but that is a simple fix.
You have a backup write location and start logging really loudly that
you are using it.

Sincerely,

JD

--
Command Prompt, Inc. - http://www.commandprompt.com/ 509-416-6579
PostgreSQL Support, Training, Professional Services and Development
High Availability, Oracle Conversion, Postgres-XC, @cmdpromptinc
For my dreams of your image that blossoms
a rose in the deeps of my heart. - W.B. Yeats

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message 李海龙 2013-06-06 03:33:11 Re: I s this a bug of spgist index in a heavy write condition?
Previous Message Joshua D. Drake 2013-06-06 03:20:22 Re: Redesigning checkpoint_segments