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

Re: mysql to postgresql, performance questions

From: Magnus Hagander <magnus(at)hagander(dot)net>
To: Stephen Frost <sfrost(at)snowman(dot)net>
Cc: Corin <wakathane(at)gmail(dot)com>, pgsql-performance <pgsql-performance(at)postgresql(dot)org>
Subject: Re: mysql to postgresql, performance questions
Date: 2010-03-18 15:23:09
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Thu, Mar 18, 2010 at 16:09, Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> Corin,
> * Corin (wakathane(at)gmail(dot)com) wrote:
>> {"QUERY PLAN"=>"Total runtime: 5.847 ms"}
> This runtime is the amount of time it took for the backend to run the
> query.
>> 44.173002243042
> These times are including all the time required to get the data back to
> the client.  If you don't use cursors, all data from the query is
> returned all at once.  Can you post the script you're using along with
> the table schema and maybe some sample or example data?  Also, are you
> doing this all inside a single transaction, or are you creating a new
> transaction for every query?  I trust you're not reconnecting to the
> database for every query..

Just as a note here, since the OP is using Debian. If you are
connecting over TCP, debian will by default to SSL on your connection
which obviously adds a *lot* of overhead. If you're not actively using
it (in which case you will control this from pg_hba.conf), just edit
postgresql.conf and disable SSL, then restart the server.

 Magnus Hagander

In response to

pgsql-performance by date

Next:From: Scott MarloweDate: 2010-03-18 15:50:16
Subject: Re: mysql to postgresql, performance questions
Previous:From: Greg SmithDate: 2010-03-18 15:16:35
Subject: Re: shared_buffers advice

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