I will report back on this and attempt to give the particulars. It
will take 24 hours due to other time commitments.
Thank you very much for explaining :) this to me.
When I used only the first 10,000 rows of the 100+ thousand rows in
the original table (of two tables) I was working with,
In response to Andreas Kretschmer :
> Bill Moran wrote:
>
> > > No, not really. But you can (and should) run EXPLAIN to
> > > obtain the execution plan for that query, und you can show us this plan
> > > (and the table-definition for all included tables). Maybe someone is able
> > > to tell you
Bill Moran wrote:
> > No, not really. But you can (and should) run EXPLAIN to
> > obtain the execution plan for that query, und you can show us this plan
> > (and the table-definition for all included tables). Maybe someone is able
> > to tell you what you can do to speed up your query.
>
> To
In response to "A. Kretschmer" :
> In response to John Gage :
> > I ran a query out of pgAdmin, and (as I expected) it took a long
> > time. In fact, I did not let it finish. I stopped it after a little
> > over an hour.
> >
> > I'm using 8.4.2 on a Mac with a 2.4GHz processor and 2GB of RA
In response to John Gage :
> I ran a query out of pgAdmin, and (as I expected) it took a long
> time. In fact, I did not let it finish. I stopped it after a little
> over an hour.
>
> I'm using 8.4.2 on a Mac with a 2.4GHz processor and 2GB of RAM.
>
> My question is: is there a way to tell
I ran a query out of pgAdmin, and (as I expected) it took a long
time. In fact, I did not let it finish. I stopped it after a little
over an hour.
I'm using 8.4.2 on a Mac with a 2.4GHz processor and 2GB of RAM.
My question is: is there a way to tell how close the query is to being
finis
