Re: Re: Just trying to read first row in table based on index, pg scans and sorts instead?

From: Steve Crawford <scrawford(at)pinpointresearch(dot)com>
To: johnmudd <johnbmudd(at)gmail(dot)com>
Cc: pgsql-novice(at)postgresql(dot)org
Subject: Re: Re: Just trying to read first row in table based on index, pg scans and sorts instead?
Date: 2012-04-19 23:31:48
Message-ID: 4F90A064.90901@pinpointresearch.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On 04/19/2012 03:58 PM, johnmudd wrote:
> Thanks, that fixed it! That's good news. The bad news is that I had made it a
> rule to add the parens because a similar query would "ignore" the an index
> if I left the parens off. I'll try to did up the counter example. It was for
> a different table, index.
When you find it, be sure to include the full description of both
tables. Is it possible that you used a bit of a different
parenthesization, if there is such a word, when you created the
different indexes?

Cheers,
Steve

In response to

Responses

Browse pgsql-novice by date

  From Date Subject
Next Message johnmudd 2012-04-20 02:31:10 Re: Just trying to read first row in table based on index, pg scans and sorts instead?
Previous Message johnmudd 2012-04-19 22:58:19 Re: Just trying to read first row in table based on index, pg scans and sorts instead?