| Hannu Krosing 2005-08-10, 7:25 am |
| I'm seeing 'query too complex' errors again.
Last time I saw was a long time ago, after I had done several subscribe
attempts that were rolled back and it generated 500Mb query when I
finally got past the subscribe step.
This time I get the same symptoms after doing a subscribe of a set with
7 tables one of them over 2M. the subscribe itself took between 30 and
60 minutes, but it still managest to make the query too big/complex .
This query is "too complex" for the master (actually forwarding
subscriber) which runs pg7.4.5, the final subscriber is running pg8.0.3
The "complex" query is about 200Mb and looks like this
declare LOG cursor for
select log_origin, log_xid, log_tableid, log_actionseq,
log_cmdtype, log_cmddata
from "_balance_cluster".sl_log_1
where log_origin = 1
and ( (log_tableid in
(1046,1048,1041,1037
,1035,1031,1021,1016
,1013,1011,1010,1009
,1003,1002,1018,1019
,1032,1012,1023,1030
,1029,1028,1027,1026
,1025,1
and ( log_xid < '1122646369'
and "_balance_cluster". xxid_lt_snapshot(log
_xid,
'1122646097:11226463
69:''1122646367'',''
1122646363'',''11226
46341'',''1122646097
'',''11226
)
and ( log_xid >= '1122645550'
and "_balance_cluster". xxid_ge_snapshot(log
_xid,
'1122645550:11226455
52:''1122645550''')
)
)
or
( log_tableid in (3,9008,9007,9005,90
04,2002,2001)
and ( log_xid < '1122646369'
and "_balance_cluster". xxid_lt_snapshot(log
_xid,
'1122646097:11226463
69:''1122646367'',''
1122646363'',''11226
46341'',''1122646097
'',''11226
)
and ( log_xid >= '1122645804')
and log_actionseq not in ('376213267','376213
268',
..this in list has ~16000 integers and is 192492 characters long.. )
)
)
order by log_actionseq;
What is it slon is trying to exclude with "log_actionseq not in(...)" ?
Any good advice for moving forward or am I stuck with this one ?
--
Hannu Krosing <hannu-7C/ iILuz2RdeoWH0uzbU5w@
public.gmane.org>
|