Re: cannot stat `/usr/local/pgsql/data/pg_xlog/00000001000000430000009C': No such file or directory

Поиск
Список
Период
Сортировка
От Denis
Тема Re: cannot stat `/usr/local/pgsql/data/pg_xlog/00000001000000430000009C': No such file or directory
Дата
Msg-id djjm4g$26p2$1@news.hub.org
обсуждение исходный текст
Ответ на cannot stat `/usr/local/pgsql/data/pg_xlog/00000001000000430000009C': No such file or directory  ("Sailer, Denis (YBUSA-CDR)" <Denis.Sailer@Yellowbook.com>)
Список pgsql-general
Ok, I figured out how to get the archiver going again.  This is what I have
in the postgresql.conf file.

archive_command = 'yblogger %p </dev/null'

I temporarily modified the script to not return failure when the source file
does not exist.
I still don't understand why postgres would attempt to archive wal files
that don't exist.  Any wal prior to issuing the pg_resetxlog should be
treated as not needed.


""Sailer, Denis (YBUSA-CDR)"" <Denis.Sailer@Yellowbook.com> wrote in message
news:3FB3AAE149F4AD4D8499E15EE8CF41A38F4572@YBCDREX01.corp.ybusa.net...
In my development system the file system where $PGDATA resides filled up.

cp: writing
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000076': No
space left on device
could not copy /usr/local/pgsql/data/pg_xlog/000000010000004300000076 to
archive
2005-10-23 08:46:29 CDTLOG:  archive command "yblogger
/usr/local/pgsql/data/pg_xlog/000000010000004300000076 </dev/null" failed:
return code 25088
cp: overwrite
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000076'?
2005-10-23 08:46:30 CDTLOG:  archived transaction log file "000000010
000004300000076"
2005-10-23 08:46:31 CDTLOG:  could not close temporary statistics file
"/usr/local/pgsql/data/global/pgstat.tmp.27235": No space left on device
cp: writing
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000077': No
space left on device
could not copy /usr/local/pgsql/data/pg_xlog/000000010000004300000077 to
archive
2005-10-23 08:47:46 CDTLOG:  archive command "yblogger
/usr/local/pgsql/data/pg_xlog/000000010000004300000077 </dev/null" failed:
return code 25088
cp: overwrite
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000077'?
2005-10-23 08:47:47 CDTLOG:  archived transaction log file "000000010
000004300000077"
2005-10-23 08:47:48 CDTLOG:  could not close temporary statistics file
"/usr/local/pgsql/data/global/pgstat.tmp.27235": No space left on device
cp: writing
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000078': No
space left on device
could not copy /usr/local/pgsql/data/pg_xlog/000000010000004300000078 to
archive
2005-10-23 08:49:49 CDTLOG:  archive command "yblogger
/usr/local/pgsql/data/pg_xlog/000000010000004300000078 </dev/null" failed:
return code 25088
cp: overwrite
`/usr/local/pgsql/archlog/ybcdrdbd01/data/000000010000004300000078'?
2005-10-23 08:49:51 CDTLOG:  archived transaction log file "000000010
000004300000078"
2005-10-23 08:49:52 CDTLOG:  could not close temporary statistics file
"/usr/local/pgsql/data/global/pgstat.tmp.27235": No space left on device
cp: writ


At this point in time postgres had gone away.  I tried to restart Postgres,
but received these messages.  Postgres would not start.


2005-10-24 08:28:04 CDTLOG:  database system was interrupted at 2005-10-23
10:01:14 CDT
2005-10-24 08:28:04 CDTLOG:  could not open file
"/usr/local/pgsql/data/pg_xlog/000000010000004300000043" (log file 67,
segment 67): No such file or dir
ectory
2005-10-24 08:28:04 CDTLOG:  invalid checkpoint record
2005-10-24 08:28:04 CDTPANIC:  could not locate required checkpoint record
2005-10-24 08:28:04 CDTHINT:  If you are not restoring from a backup, try
removing the file "/usr/local/pgsql/data/backup_label".
2005-10-24 08:28:04 CDTLOG:  startup process (PID 13345) was terminated by
signal 6
2005-10-24 08:28:04 CDTLOG:  aborting startup due to startup process failure
2005-10-24 08:28:04 CDTLOG:  logger shutting down


Since this is development I used "pg_resetxlog -f /usr/local/pgsql/data".  I
then tried to start Postgres, but received the same messages as above.  I
removed the backup in progress file as stated in the message.  Postgres was
able to start after that, but now it keeps trying to archive log files that
don't exist.

How can I tell postgres to move to the point in time where log file
truncation occurred where the log files now start?



В списке pgsql-general по дате отправления:

Предыдущее
От: Jeff Davis
Дата:
Сообщение: Re: PostgreSQL vs mySQL, any performance difference for
Следующее
От: "Rafael Montoya"
Дата:
Сообщение: Re: function DECODE and triggers