From: | Simon Riggs <simon(at)2ndQuadrant(dot)com> |
---|---|
To: | Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Hot standby, recovery infra |
Date: | 2009-01-31 09:25:49 |
Message-ID: | 1233393949.4500.11.camel@ebony.2ndQuadrant |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Fri, 2009-01-30 at 13:15 +0200, Heikki Linnakangas wrote:
> Simon Riggs wrote:
> > I'm thinking to add a new function that will allow crash testing easier.
> >
> > pg_crash_standby() will issue a new xlog record, XLOG_CRASH_STANDBY,
> > which when replayed will just throw a FATAL error and crash Startup
> > process. We won't be adding that to the user docs...
> >
> > This will allow us to produce tests that crash the server at specific
> > places, rather than trying to trap those points manually.
>
> Heh, talk about a footgun ;-). I don't think including that in CVS is a
> good idea.
Thought you'd like it. I'd have preferred it in a plugin... :-(
Not really sure why its a problem though. We support
pg_ctl stop -m immediate, which is the equivalent, yet we don't regard
that as a footgun.
--
Simon Riggs www.2ndQuadrant.com
PostgreSQL Training, Services and Support
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2009-01-31 09:27:08 | Re: Hot standby, recovery infra |
Previous Message | Simon Riggs | 2009-01-31 09:21:39 | Re: [PATCH] Space reservation v02 |