| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Fujii Masao <masao(dot)fujii(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: warning message in standby |
| Date: | 2010-06-12 01:19:19 |
| Message-ID: | 201006120119.o5C1JJr11129@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> > If my streaming replication stops working, I want to know about it as
> > soon as possible. WARNING just doesn't cut it.
> >
> > This needs some better thought.
> >
> > If we PANIC, then surely it will PANIC again when we restart unless we
> > do something. So we can't do that. But we need to do something better
> > than
> >
> > WARNING there is a bug that will likely cause major data loss
> > HINT you'll be sacked if you miss this message
>
> +1. I was making this same argument (less eloquently) upthread.
> I particularly like the errhint().
I am wondering what action would be most likely to get the
administrator's attention.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ None of us is going to be here forever. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Rafael Martinez | 2010-06-12 01:29:04 | 9.0beta2 - server crash when using HS + SR |
| Previous Message | Josh Berkus | 2010-06-12 01:10:18 | Re: Proposal for 9.1: WAL streaming from WAL buffers |