Re: does wal archiving block the current client connection?
От | Simon Riggs |
---|---|
Тема | Re: does wal archiving block the current client connection? |
Дата | |
Msg-id | 1147942877.2646.388.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: does wal archiving block the current client connection? (Jeff Frost <jeff@frostconsultingllc.com>) |
Ответы |
Re: does wal archiving block the current client connection?
|
Список | pgsql-admin |
On Wed, 2006-05-17 at 22:45 -0700, Jeff Frost wrote: > On Thu, 18 May 2006, Tom Lane wrote: > > > Jeff Frost <jeff@frostconsultingllc.com> writes: > >> I seem to get alot of these: > > > >> May 17 21:34:04 discord postgres[20573]: [5-1] WARNING: could not rename file > >> "pg_xlog/archive_status/000000010000000000000001.ready" to > >> May 17 21:34:04 discord postgres[20573]: [5-2] > >> "pg_xlog/archive_status/000000010000000000000001.done": No such file or > >> directory > > > > That seems odd ... > > Further interesting items: > > May 17 22:41:18 discord postgres[23817]: [3-1] LOG: archive command > "/usr/local/pgsql-8.1.3/bin/archive_test.sh "pg_xlog/00000001000000000000000E" > "00000001000000000000000E"" > May 17 22:41:18 discord postgres[23817]: [3-2] failed: return code 256 > And in the window where I started postgres via pg_ctl, I had this: > > cat: pg_xlog/00000001000000000000000E: No such file or directory > cat: pg_xlog/00000001000000000000000E: No such file or directory > > Seems bad. Seems so. Can you post the full test, plus full execution log. [You don't need to "cat" you could just do "ls" instead FWIW] Are you doing *anything* with pg_xlog directory or below? I understand your saying No to that question and pg_xlog has not been moved, its just underneath data directory, which is on normal disk? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
В списке pgsql-admin по дате отправления: