Thread: log entries after pitr recovery
I have been testing pitr with my development system. After the system rolled forward, I recieve a ton of errors right after it come on line. I'm assuming these are fine and just the system cleaning up, but I wanted to make sure.
Thanks,
Chris
,11962,,2006-07-13 16:11:16.281 EDT,,360,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11:16.281 EDT,,361,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11: 16.281 EDT,,362,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11:16.281 EDT,,363,,,,LOG: invalid server process ID -1
Thanks,
Chris
,11962,,2006-07-13 16:11:16.281 EDT,,360,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11:16.281 EDT,,361,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11: 16.281 EDT,,362,,,,LOG: invalid server process ID -1
,11962,,2006-07-13 16:11:16.281 EDT,,363,,,,LOG: invalid server process ID -1
"Chris Hoover" <revoohc@gmail.com> writes: > ,11962,,2006-07-13 16:11:16.281 EDT,,360,,,,LOG: invalid server process ID > -1 See 8.1.4 fix: 2006-03-30 17:11 tgl * src/backend/storage/smgr/smgr.c (REL8_1_STABLE): Suppress attempts to report dropped tables to the stats collector from a startup or recovery process. Since such a process isn't a real backend, pgstat.c gets confused. This accounts for recent reports of strange "invalid server process ID -1" log messages during crash recovery. There isn't any point in attempting to make the report, since we'll discard stats in such scenarios anyhow. regards, tom lane