Re: BUG #1393: Adding 'LIMIT 1' to the query halts forever

From: "Fahad G(dot)" <Fahad(dot)Gilani(at)anusf(dot)anu(dot)edu(dot)au>
To: Michael Fuhr <mike(at)fuhr(dot)org>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #1393: Adding 'LIMIT 1' to the query halts forever
Date: 2005-01-16 01:36:40
Message-ID: BE101058.20D5%Fahad.Gilani@anusf.anu.edu.au
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Michael,

On 16/1/05 12:48 AM, "Michael Fuhr" <mike(at)fuhr(dot)org> wrote:

> On Fri, Jan 14, 2005 at 11:31:05PM -0500, Tom Lane wrote:
>> "Fahad G." <Fahad(dot)Gilani(at)anusf(dot)anu(dot)edu(dot)au> writes:
>>> -- Indexes
>>> CREATE INDEX jobstat_lc_q4_2004_jobid ON jobstat_lc_q4_2004 USING btree
>>> (jobid);
>>> CREATE INDEX jobstat_lc_q4_2004_fetchtime ON jobstat_lc_q4_2004 USING btree
>>> (fetchtime);
>>> CREATE UNIQUE INDEX jobstat_lc_q4_2004_walltime ON
>>> unq_jobstat_lc_q4_2004_jobid_fetch USING btree (jobid, fetchtime);
>
> The last index is created on a different table -- should it be
> created on the table we're working with? And if so, are the columns
> (jobid, fetchtime) correct? The index name suggests otherwise.
>

I'm sorry. My mistake again while copying indexes from the log. The index
is:

CREATE UNIQUE INDEX unq_jobstat_lc_q4_2004_jobid_fetch ON jobstat_lc_q4_2004
USING btree( jobid, fetchtime);

So basically the unique index is on the same table.

Regards,
Fahad
--
main(){int j=12345;char t[]=":aAbcdefFgGhijklmnNopqrsStuUvwyz \n",
*i="dUGScUiAbpmwqbmgduAvpmmlzce\nlmGGUbFbzjdb";while(*i){j+=
strchr(t,*i++)-t;j%=sizeof t-1;putchar(t[j]);}return 0;}

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message tayarain 2005-01-16 02:41:51 help
Previous Message gonzaga 2005-01-15 20:08:23 Bug in check constraint?