Re: Hard limit on WAL space used (because PANIC sucks)

From: Claudio Freire <klaussfreire(at)gmail(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: MauMau <maumau307(at)gmail(dot)com>, Daniel Farina <daniel(at)heroku(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-Dev <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Hard limit on WAL space used (because PANIC sucks)
Date: 2013-06-12 15:11:42
Message-ID: CAGTBQpZ+X0n8SB3qSmkXXryMeCx1Ae4WvjC6Q+QCOiZONo0zgA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Jun 12, 2013 at 11:55 AM, Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
>> I hope PostgreSQL will provide a reliable archiving facility that is ready
>> to use.
>
> +1. I think we should have a way to set an archive DIRECTORY, rather
> than an archive command. And if you set it, then PostgreSQL should
> just do all of that stuff correctly, without any help from the user.
> Of course, some users will want to archive to a remote machine via ssh
> or rsync or what-have-you, and those users will need to provide their
> own tools. But it's got to be pretty common to archive to a local
> path that happens to be a remote mount, or to a local directory whose
> contents are subsequently copied off by a batch job. Making that work
> nicely with near-zero configuration would be a significant advance.

That, or provide a standard archive command that takes the directory
as argument?

I bet we have tons of those available among us users...

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2013-06-12 15:12:58 Re: Adding IEEE 754:2008 decimal floating point and hardware support for it
Previous Message Tom Lane 2013-06-12 15:10:20 Re: Configurable location for extension .control files