Re: query planning different in plpgsql?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: Scott Mead <scott.lists@xxxxxxxxxxxxxxxx>
Subject: Re: query planning different in plpgsql?
From: Grzegorz Jaśkiewicz <gryzman@xxxxxxxxx>
Date: Fri, 23 Oct 2009 16:56:36 +0100
Cc: "Michal J. Kubski" <michal.kubski@xxxxxx>, pgsql-performance@xxxxxxxxxxxxxx
In-reply-to: <d3ab2ec80910230849i509763y35def24361bf3e7e@xxxxxxxxxxxxxx>
References: <a99402025047afbcc210461b220d9b64@localhost> <d3ab2ec80910230849i509763y35def24361bf3e7e@xxxxxxxxxxxxxx>

On Fri, Oct 23, 2009 at 4:49 PM, Scott Mead <scott.lists@xxxxxxxxxxxxxxxx> wrote:

Do you not have an index on last_snapshot.domain_id?

that, and also try rewriting a query as JOIN. There might be difference in performance/plan.

--
GJ

Follow-Ups:
- Re: query planning different in plpgsql?
  - From: Michal J. Kubski

References:
- query planning different in plpgsql?
  - From: Michal J. Kubski
- Re: query planning different in plpgsql?
  - From: Scott Mead

Prev by Date: Re: Queryplan within FTS/GIN index -search.
Next by Date: Re: Queryplan within FTS/GIN index -search.
Previous by thread: Re: query planning different in plpgsql?
Next by thread: Re: query planning different in plpgsql?
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux