Skip site navigation (1) Skip section navigation (2)

Re: scale up (postgresql vs mssql)

From: Robert Klemme <shortcutter(at)googlemail(dot)com>
To: Merlin Moncure <mmoncure(at)gmail(dot)com>
Cc: Eyal Wilde <eyal(at)impactsoft(dot)co(dot)il>, pgsql-performance(at)postgresql(dot)org
Subject: Re: scale up (postgresql vs mssql)
Date: 2012-05-09 07:11:42
Message-ID: CAM9pMnNxRQC73wmBKOwSgyBH1X-p0Z1n=hAxmLmT1owN18TZOA@mail.gmail.com (view raw or flat)
Thread:
Lists: pgsql-performance
On Fri, May 4, 2012 at 3:04 PM, Merlin Moncure <mmoncure(at)gmail(dot)com> wrote:

> let's see the query plan...when you turned it off, did it go faster?
> put your suspicious plans here: http://explain.depesz.com/

I suggest to post three plans:

1. insert into temp table
2. access to temp table before analyze
3. access to temp table after analyze

Maybe getting rid of the temp table (e.g. using a view or even an
inline view) is even better than optimizing temp table access.

Kind regards

robert

-- 
remember.guy do |as, often| as.you_can - without end
http://blog.rubybestpractices.com/

In response to

Responses

pgsql-performance by date

Next:From: Merlin MoncureDate: 2012-05-09 12:53:01
Subject: Re: scale up (postgresql vs mssql)
Previous:From: Robert HaasDate: 2012-05-08 16:17:55
Subject: Re: Sudden Query slowdown on our Postgresql Server

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group