Re: warning message in standby
Bruce Momjian <bruce@momjian.us>
From: Bruce Momjian <bruce@momjian.us>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Simon Riggs <simon@2ndquadrant.com>, Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>, Tom Lane <tgl@sss.pgh.pa.us>, Fujii Masao <masao.fujii@gmail.com>, PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2010-06-12T01:19:19Z
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@momjian.us> http://momjian.us EnterpriseDB http://enterprisedb.com + None of us is going to be here forever. +