> >> I'm guessing this is a variant of the problem Philip 
> >> Warner reported yesterday.  Probably WAL-related.  Vadim?
> 
> > Probably, though I don't understand how WAL is related to 
> > execution plans. Ok, it's easy to reproduce - I'll take a look.
> 
> Could just be a question of a different pattern of table accesses?
> Let me know if you want help looking...

Fixed - fdstate was not properly setted in fd.c:fileNameOpenFile
with WAL enabled, sorry.

Philip, please try to reproduce crash.

Vadim

Reply via email to