> I get the feeling that what we will see is the destination
> filename already present and the source not, which would suggest
> that two backends tried to do the rename concurrently.
Tom,
I just noticed that the rename panic errors like this one:
PANIC: rename from /data/pg_xlog/00030
"Yurgis Baykshtis" <[EMAIL PROTECTED]> writes:
> I just noticed that the rename panic errors like this one:
> PANIC: rename from /data/pg_xlog/0003001F to
> /data/pg_xlog/0003002C (initialization of log file 3, segment 44)
> failed: No such file or directory
> come shortly AFTER
"Yurgis Baykshtis" <[EMAIL PROTECTED]> writes:
> The most interesting thing is that rename failure is always followed by
> IpcMemoryCreate and vice-versa, IpcMemoryCreate always comes after the
> rename error.
That is not "interesting" ... it's exactly what I'd expect for the panic
recovery sequen
"Yurgis Baykshtis" <[EMAIL PROTECTED]> writes:
> However, we still experience random PG failures on a weekly basis.
> PANIC: rename from /data/pg_xlog/00220009 to
> /data/pg_xlog/00220012 (initialization of log file 34, segment 18)
> failed: No such file or directory
That's curio
