| From: | Christoph Moench-Tegeder <cmt(at)burggraben(dot)net> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Logging the fact that a log was shipped |
| Date: | 2017-08-28 11:06:31 |
| Message-ID: | 20170828110630.tb4ealny7kq6voms@squirrel.exwg.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
## Ron Johnson (ron(dot)l(dot)johnson(at)cox(dot)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.
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...
Regards,
Christoph
--
Spare Space.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alban Hertroys | 2017-08-28 12:22:50 | Performance with high correlation in group by on PK |
| Previous Message | Moreno Andreo | 2017-08-28 08:54:45 | Re: [SPAM] Re: Invalid magic number 0000 in log file |