We have noticed this line in our server log:
Redo record at (5, 4209179252); Undo record at (0, 0); Shutdown TRUE
That second number seems awfully high; should this give us cause for
concern?
You'll see (6, small number) soon.
Vadim
---(end of
In 7.1.3 and 7.2, there are only 2-3 WAL files kept because
there is no need to keep them after a checkpoint. Is there
any need to have these WAL config paramaters anymore?
I missed what's you propose to remove.
I am not proposing to remove anything. I just want to make sure
i just upgraded my database system from 7.0.3 to 7.1 ... i
did a dumpall and psql -f dump.sql to the new db. the data
is in place correctly and its running fine. but as soon as
i put the connections back on to the db the load raised to
6. prior to the upgrade the system load was an 0.3 ...
Hmm ... so you think the people who have complained of this are all
working with databases that have suffered previous crash corruption?
I doubt it. There's too much consistency to the reports: in
particular, it's generally triggered by creation of lots of large
objects, and it's always the
Warning: PostgreSQL query failed: FATAL 1: my bits moved
right off the end of the world! Recreate index
pg_attribute_relid_attnum_index.
This is an internal "can't happen" failure condition,
presumably arising from some weird corner-case bug in btree
index manipulation. We have seen
I tried, but nothing has changed !
The strangest is I have a database which was not accessed
sinc several days and even this one does not function
in pg_class, I see for exemple that one on my table has
ntuples=1800 but I can't access it...
Oh, so you're able to select from your
I've searched the documentation and the mailing lists archive but I'm
unable to find info on setting checkpoints and performing roll-forward
operations with the transaction log. I'd appreciate it if
someone could point me to the right docs.
WAL stuff is not documented yet.
Anyway you
