On 9/22/07, Tom Lane <tgl@xxxxxxxxxxxxx> wrote: > "Morris Goldstein" <morris.x.goldstein@xxxxxxxxx> writes: > > ... > > 2007-09-22 07:06:05 [3060] LOG: could not open file > > "/var/lib/pgsql/data/pg_xlog/0000000000000000" (log file 0, segment 0): No such file or directory > > ... > > ... > > You might be able to recover, at least to the extent of getting some > data out of these DBs, by using pg_resetxlog. Read its man page > *carefully* beforehand. > http://www.postgresql.org/docs/7.4/static/app-pgresetxlog.html I looked at the pg_resetxlog documentation and have a question. Here is output from pg_resetxlog -n: pg_control values: pg_control version number: 72 Catalog version number: 200310211 Current log file ID: 0 Next log file segment: 1 Latest checkpoint's StartUpID: 12 Latest checkpoint's NextXID: 536 Latest checkpoint's NextOID: 17142 Database block size: 8192 Blocks per segment of large relation: 131072 Maximum length of identifiers: 64 Maximum number of function arguments: 32 Date/time type storage: floating-point numbers Maximum length of locale name: 128 LC_COLLATE: C LC_CTYPE: C Is it safe to run pg_resetxlog without the -l argument? Or should I specify -l, constructing an argument from the last pg_xlog filename? Morris ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org/
