On Wed, Aug 3, 2016 at 8:46 AM Christophe Pettus <[email protected]> wrote:
> > On Aug 3, 2016, at 8:43 AM, Steve V <[email protected]> wrote: > > I'm wondering if the abnormal exit was the archive_command? > > The archive_command doesn't actually connect to a PostgreSQL backend, so > it wouldn't produce a backend crash. (archive_command failures, if they > result in output to stderr, are in the .log file.) > > It's probably a coincidence; some other connection caused a backend crash > which caused a PostgreSQL restart. > Agree. WAL-E doesn't send signals or do anything as the poster describes anyway. If one must venture a guess, perhaps memory pressure may be in play? Check for OOMs in syslog. -- You received this message because you are subscribed to the Google Groups "wal-e" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
