| From: | Daniel Farina <daniel(at)heroku(dot)com> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Hard limit on WAL space used (because PANIC sucks) |
| Date: | 2013-06-07 05:41:18 |
| Message-ID: | CAAZKuFYHvaawsrLrqHsfgfByvx-Fp_fv0mrC6WboNphGrejN9A@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jun 6, 2013 at 9:30 PM, Jeff Janes <jeff(dot)janes(at)gmail(dot)com> wrote:
> I would oppose that as the solution, either an unconditional one, or
> configurable with is it as the default. Those segments are not unneeded. I
> need them. That is why I set up archiving in the first place. If you need
> to shut down the database rather than violate my established retention
> policy, then shut down the database.
Same boat. My archives are the real storage. The disks are
write-back caching. That's because the storage of my archives is
probably three to five orders of magnitude more reliable.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Kapila | 2013-06-07 06:28:14 | Re: Partitioning performance: cache stringToNode() of pg_constraint.ccbin |
| Previous Message | Joshua D. Drake | 2013-06-07 05:06:43 | Re: Hard limit on WAL space used (because PANIC sucks) |