| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | Fujii Masao <masao(dot)fujii(at)gmail(dot)com> |
| Cc: | Erik Rijkers <er(at)xs4all(dot)nl>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: testing cvs HEAD - HS/SR - cannot stat |
| Date: | 2010-02-04 18:22:23 |
| Message-ID: | 4B6B105F.8000007@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Yeah, this is not a bug.
>
> At first, the standby performs an archive recovery until an invalid
> WAL record is found. Then it starts replication and tries to receive
> the missing WAL records from the primary. So such an error message
> would be logged whenever an invalid record is found and replication
> is started.
Can we improve the error message? Right now it's alarming people. Such as:
cannot stat
`/var/data1/pg_stuff/dump/replication_archive/000000010000000000000002':
End of Log
Of course, it would be even better to supress this error message
entirely unless the user is at DEBUG1 or better.
--Josh Berkus
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ivan Sergio Borgonovo | 2010-02-04 18:24:02 | building tsquery directly in memory (avoid makepol) |
| Previous Message | Simon Riggs | 2010-02-04 18:21:24 | Re: Re: [COMMITTERS] pgsql: Assorted cleanups in preparation for using a map file to support |