Op 27/10/2015 om 15:32:46 +0100, schreef David Steele:
> On 10/27/15 3:16 PM, Leo Baltus wrote:
> >postgresql-9.4.5
> >
> >When running pg_stop_backup() psql outputs on stderr:
> >
> >NOTICE: pg_stop_backup complete, all required WAL segments have been
> >a
postgresql-9.4.5
When running pg_stop_backup() psql outputs on stderr:
NOTICE: pg_stop_backup complete, all required WAL segments have been archived
--quiet does not seem to suppress it, what does?
I really hate to redirect stderr to /dev/null.
--
Leo Baltus, internetbeheerder
NPO ICT
postgresql-9.4.5
When running pg_stop_backup() psql outputs on stderr:
NOTICE: pg_stop_backup complete, all required WAL segments have been archived
--quiet does not seem to suppress it, what does?
I really hate to redirect stderr to /dev/null.
--
Leo Baltus, internetbeheerder
NPO ICT
Op 08/08/2015 om 14:24:00 -0400, schreef David Steele:
> On 8/7/15 7:01 AM, Leo Baltus wrote:
> >While backing up some postgresql-8.4.2 instances using
> >pg_start_backup()/pg_stop_backup()
> >
> >We noticed that sometimes rsync complains:
> >
> >file has va
re what to believe, either
- my backup was invalid and I have to take measures to prevent this
(and file a bug report)
- I can ignore this *and* can safely exclude pg_trans/ from my backups.
- there is some other workaround...
--
Leo Baltus
--
Sent via pgsql-general mailing list (pgs
