Re: [GENERAL] Logging the fact that a log was shipped - Mailing list pgsql-general

From Ron Johnson
Subject Re: [GENERAL] Logging the fact that a log was shipped
Date
Msg-id 4052872e-9dd9-4184-b418-ee0cf78b09e9@cox.net
Whole thread Raw
In response to [GENERAL] Logging the fact that a log was shipped  (Ron Johnson <ron.l.johnson@cox.net>)
Responses Re: [GENERAL] Logging the fact that a log was shipped  (Christoph Moench-Tegeder <cmt@burggraben.net>)
List pgsql-general
On 08/28/2017 06:06 AM, Christoph Moench-Tegeder wrote:
> ## Ron Johnson (ron.l.johnson@cox.net):
>
>> How is this done in v8.4?  (I tried adding "date; rsync ..." but pg
>> didn't like that *at all*.)
> There's a DEBUG1-level log message on successful archive_command
> completion - that would give you a lot of other low-prio log
> messages wich you probably don't care about.
> I'd put a wrapper around your rsync (a short shell script
> would be sufficient) in the lines of rsync ... && logger "done",
> that way you'd get the information via syslog.

And if logging to stderr?

> On the other hand, do you really need the details about each WAL
> segment? Since 9.4 there's pg_stat_wal_archiver... You're really
> making your job harder than it needs to be with that ancient
> PostgreSQL...

That's far beyond my control.

--
World Peace Through Nuclear Pacification



pgsql-general by date:

Previous
From: Alban Hertroys
Date:
Subject: Re: [GENERAL] Performance with high correlation in group by on PK
Next
From: Stephen Frost
Date:
Subject: Re: [GENERAL] Logging the fact that a log was shipped