Heikki Linnakangas escribió: > When recovery reaches an invalid WAL record, typically caused by a > half-written WAL file, it closes the file and moves to the next source. > If an error is found in a file restored from archive or in a portion > just streamed from master, however, a PANIC is thrown, because it's not > expected to have errors in the archive or in the master.
Hmm, I think I've heard that tools like walmgr do incremental copies of the current WAL segment to the archive. Doesn't this change break that? (Maybe I'm confused and it doesn't work that way) -- Alvaro Herrera http://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
