On 6/30/06, Tom Lane <[EMAIL PROTECTED]> wrote:
I don't know the kernel nearly well enough to guess if these are related ...
The sl_log_* tables are indexed on xid, where the relations between values are not exactly stable. When having high enough activity on one node or having nodes with XIDs on different enough positions funny things happen. Have you already excluded this as a probable reason? -- marko ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match