> What did make me scratch my head was a short stream of @ symbols (well they
> show up as @ symbols in vi) in the log file of the main server (others are
> slony subscribers).
>
> mentioning those @ symbols ...
1,5 weeks ago there was reported on this list the problem "postgres service
not st
> --- On Thu, 7/5/09, Massa, Harald Armin wrote:
> > After reading the answers to the funny chars in the logs and no fsync on
> > the logs: is there a fsync on postmaster.pid? Or is that file not
> > considered important enough?
I think this strongly suggests that postmaster.pid should be fsync
--- On Thu, 7/5/09, Massa, Harald Armin wrote:
> >
> > mentioning those @ symbols ...
>
> 1,5 weeks ago there was reported on this list the problem
> "postgres service
> not starting on windows"; after consulting event log
> the user reported as
> message "bogus data in postmaster.pid". Aft
Glyn Astill wrote:
> We had a power outage today when a couple of computer
> controlled power strips crashed (my secondary psu's will stay
> firmly in the wall sockets now though).
>
> I'd had a lot of fun pulling plugs out under load before we
> went into production so I wasn't particularly wo
> From: Albe Laurenz
> Subject: RE: [GENERAL] Power outage and funny chars in the logs
> To: glynast...@yahoo.co.uk, pgsql-general@postgresql.org
> Date: Thursday, 7 May, 2009, 2:44 PM
> Glyn Astill wrote:
> > We had a power outage today when a couple of computer
>
>
Glyn Astill writes:
> What did make me scratch my head was a short stream of @ symbols (well they
> show up as @ symbols in vi) in the log file of the main server (others are
> slony subscribers).
There isn't anything making any effort to fsync the postmaster log, so
some data corruption in the
Hi chaps,
We had a power outage today when a couple of computer controlled power strips
crashed (my secondary psu's will stay firmly in the wall sockets now though).
I'd had a lot of fun pulling plugs out under load before we went into
production so I wasn't particularly worried, and the datab
