great, thanks a lot...
On Tuesday 05 May 2009 17:11:35 Tom Lane wrote:
> Marc Cousin writes:
> > On Tuesday 05 May 2009 16:35:11 Tom Lane wrote:
> >> Hmm ... is it likely that index entries with pathid = 120 are *very* few
> >> and far between in jobid order? It looks like we have no
> >> CHECK_
Marc Cousin writes:
> On Tuesday 05 May 2009 16:35:11 Tom Lane wrote:
>> Hmm ... is it likely that index entries with pathid = 120 are *very* few
>> and far between in jobid order? It looks like we have no
>> CHECK_FOR_INTERRUPTS calls inside the loop in _bt_next(), which is
>> probably a mistake
On Tuesday 05 May 2009 16:35:11 Tom Lane wrote:
> Marc Cousin writes:
> > [ can't cancel this query ]
> >
> > Index Scan using file_jpfid_idx on file (cost=0.00..7327212.07
> > rows=2128 width=104)
> >Index Cond: (pathid = 120)
> >
> > "file_jpfid_idx" btree (jobid, pathid, filenameid)
>
Marc Cousin writes:
> [ can't cancel this query ]
> Index Scan using file_jpfid_idx on file (cost=0.00..7327212.07 rows=2128
> width=104)
>Index Cond: (pathid = 120)
> "file_jpfid_idx" btree (jobid, pathid, filenameid)
Hmm ... is it likely that index entries with pathid = 120 are *ve
Hi, I'm having a problem cancelling a query.
I've already had sometimes this kind of problem, but not this hard (and I
didn't find anything searching the archives, but still I remember seeing
discussions about this). Usually, it cancels in a few seconds to a minute.
I've run this query an hou
