Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uz8Tg-0007Ub-Ve for pgsql-performance@arkaria.postgresql.org; Tue, 16 Jul 2013 16:51:53 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1Uz8Tg-0001Bb-9U for pgsql-performance@arkaria.postgresql.org; Tue, 16 Jul 2013 16:51:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uz8Tf-0001BU-7H for pgsql-performance@postgresql.org; Tue, 16 Jul 2013 16:51:51 +0000 Received: from mail-ob0-f180.google.com ([209.85.214.180]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1Uz8Tc-00078Q-4d for pgsql-performance@postgresql.org; Tue, 16 Jul 2013 16:51:50 +0000 Received: by mail-ob0-f180.google.com with SMTP id eh20so1026969obb.25 for ; Tue, 16 Jul 2013 09:51:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type:content-transfer-encoding:x-gm-message-state; bh=mKOk/7vz1umC8vGP4rdfonIZn/LOdXK3XFKzuk6pZV0=; b=IEeHUm7/Aj/NTMwM8+aU940jWwjN4FxUl+JYs8wVeW96Wk20952lW72gv2NeHXvwga 4YxjBKjEQozLl9gV/w/C7QEER6BcDLUAiVqm4wADEI9ljaa2ZswLgwUokdm+5oupzojh RPJ5fUabzzsDdRJgOQXgSy6AaNloISw4rGJHg8Gh55j73VyEHXFBrLTkIYc3LCOXr9qw HT3cXqk3MsfFz3AokNbxga/sKT/B8XdtYOBwrCPgLwrnDVLFkq+d9165YSp9KjB3A7Im RUCB2revXW5uNXrJ2tZbWb0ephoP/qD/ND5t/le907S6cJzf3mUNVf6E7ssKqmM9xw8M IP1g== X-Received: by 10.182.118.129 with SMTP id km1mr567840obb.15.1373993505685; Tue, 16 Jul 2013 09:51:45 -0700 (PDT) Received: from brianf.consistentstate.com (216-98-193-98.static.forethought.net. [216.98.193.98]) by mx.google.com with ESMTPSA id fk3sm1829550obb.2.2013.07.16.09.51.43 for (version=TLSv1 cipher=RC4-SHA bits=128/128); Tue, 16 Jul 2013 09:51:43 -0700 (PDT) Message-ID: <51E57A1E.9020309@consistentstate.com> Date: Tue, 16 Jul 2013 10:51:42 -0600 From: Brian Fehrle User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130311 Thunderbird/17.0.4 MIME-Version: 1.0 To: "pgsql-performance@postgresql.org" Subject: General key issues when comparing performance between PostgreSQL and oracle Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQnOTiSD3La6AMATZO+UP57bKK1H1N+nCQCpBltl9acnptrAl71lu7qSJ8WoD5GQiEm0emvP X-Pg-Spam-Score: -2.6 (--) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-performance Precedence: bulk Sender: pgsql-performance-owner@postgresql.org Hi all (Hopefully this is the correct mailing list for this). I'm working on performance tuning a host of queries on PostgreSQL 9.2 from an application, each query having its own issues and fixes, however from what I understand this application runs the exact same queries on the exact same data in half the time on oracle and SQL server. Are there any known differences between the database systems in terms of query planners or general operations (sorting, unions) that are notable different between the systems that would make postgres slow down when executing the exact same queries? It's worth noting that the queries are not that good, they have issues with bad sub-selects, Cartesian products, and what looks like bad query design in general, so the blame isn't completely with the database being slow, but I wonder what makes oracle preform better when given not-so-great queries? I know this is rather general and high level, but any tips or experience anyone has would be appreciated. Thanks, - Brian F -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance