Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bb4V7-0000JW-4j for pgsql-performance@arkaria.postgresql.org; Sat, 20 Aug 2016 11:31:45 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bb4V6-0000xg-E5 for pgsql-performance@arkaria.postgresql.org; Sat, 20 Aug 2016 11:31:44 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bb4V4-0000xQ-LI; Sat, 20 Aug 2016 11:31:42 +0000 Received: from md-in-15.webhostbox.net ([103.21.59.21]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bb4V0-0003b4-Pj; Sat, 20 Aug 2016 11:31:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=ipathsolutions.co.in; s=default; h=Message-ID:References:In-Reply-To: Subject:Cc:To:From:Date:Content-Transfer-Encoding:Content-Type:MIME-Version; bh=eC4E9joluzpV0x7Cki+Kx/la7BHqDsHZBSx+zfvNVAg=; b=QG8zn/rUpj0lCuD4uvYKjVCDG JMw7arNg31iRz74QDLt65umlNr4nBJrwLhpFfODEI9JCFBFswcR8swBlYvHVotb0HR0fkYiFgyybW 1ev8d9fC077SRcxDOua0DOW9SxJSj32dolIiCMN+CmeTP+0zSUHTz7vc3CNtTYkX+nWP8SAWPjoUa 619TXfaUiKsjxDQshSeBnHKQWCF8PaU18IUrH7Zr6XEeyfODBOJ3liu2ikz2NCgDNd48kM8tTauEY +Ra8uVA4fmNspAna+DA99jB2D+ioJIfZPBe3zQ/eybpd1yxkiTeFCXw20EW7IwY70Enyx+3opwqPE 5wWWyc7UQ==; Received: from [127.0.0.1] (port=53245 helo=ipathsolutions.co.in) by md-in-15.webhostbox.net with esmtpa (Exim 4.86_1) (envelope-from ) id 1bb4Uv-002gdq-03; Sat, 20 Aug 2016 11:31:34 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Sat, 20 Aug 2016 11:31:32 +0000 From: debasis.moharana@ipathsolutions.co.in To: Pavel Stehule Cc: pgsql-performance@postgresql.org, pgsql-performance-owner@postgresql.org Subject: Re: pgsql-performance issue In-Reply-To: References: Message-ID: <701d07526dd15e94a38c857b4f459194@ipathsolutions.co.in> X-Sender: debasis.moharana@ipathsolutions.co.in User-Agent: Roundcube Webmail/1.0.6 X-Authenticated_sender: debasis.moharana@ipathsolutions.co.in X-OutGoing-Spam-Status: No, score=-1.0 X-AntiAbuse: This header was added to track abuse, please include it with any abuse report X-AntiAbuse: Primary Hostname - md-in-15.webhostbox.net X-AntiAbuse: Original Domain - postgresql.org X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12] X-AntiAbuse: Sender Address Domain - ipathsolutions.co.in X-Get-Message-Sender-Via: md-in-15.webhostbox.net: authenticated_id: debasis.moharana@ipathsolutions.co.in X-Authenticated-Sender: md-in-15.webhostbox.net: debasis.moharana@ipathsolutions.co.in X-Source: X-Source-Args: X-Source-Dir: X-Pg-Spam-Score: -0.0 (/) 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 On 2016-08-20 08:58, Pavel Stehule wrote: > 2016-08-20 10:27 GMT+02:00 : > >> On 2016-08-20 08:21, pgsql-performance-owner@postgresql.org wrote: >> >>> Welcome to the pgsql-performance mailing list! >>> Your password at PostgreSQL Mailing Lists is >>> >>> x8DiA6 >>> >>> To leave this mailing list, send the following command in the >>> body >>> of a message to majordomo@postgresql.org: >>> >>> approve x8DiA6 unsubscribe pgsql-performance >>> debasis.moharana@ipathsolutions.co.in >>> >>> This command will work even if your address changes. For that >>> reason, >>> among others, it is important that you keep a copy of this >>> message. >>> >>> To post a message to the mailing list, send it to >>> pgsql-performance@postgresql.org >>> >>> If you need help or have questions about the mailing list, please >>> contact the people who manage the list by sending a message to >>> pgsql-performance-owner@postgresql.org >>> >>> You can manage your subscription by visiting the following WWW >>> location: >>> >>> >> > >> [1]> >> Dear Sir/Mam, >> >> I have a PostgreSQL 9.5 instance running on Windows 8 machine with >> 4GB of RAM.This server is mainly used for inserting/updating large >> amounts of data via copy/insert/update commands, and seldom for >> running select queries. >> >> Here are the relevant configuration parameters I changed: >> >> max_connections = 100 >> shared_buffers = 512MB >> effective_cache_size = 3GB >> work_mem = 12233kB >> maintenance_work_mem = 256MB >> min_wal_size = 1GB max_wal_size = 2GB >> checkpoint_completion_target = 0.7 >> wal_buffers = 16MB >> default_statistics_target = 100 >> >> After setting in postgresql.conf. I run the select query to fetch >> large amount of record of 29000 in postgresql but it takes 10.3 >> seconds but the same query takes 2 seconds for execution in MSSQL. >> >> So my query is how to improve the perfermance in postgresql. > > hi > > please, send execution plan of slow query > > https://www.postgresql.org/docs/current/static/sql-explain.html [3] > https://explain.depesz.com/ [4] > > p.s. Did you do VACUUM and ANALYZE on database? > > Regards > > Pavel > >> Regards, >> Debasis Moharana >> .NET Software Developer >> >> -- >> Sent via pgsql-performance mailing list >> (pgsql-performance@postgresql.org) >> To make changes to your subscription: >> http://www.postgresql.org/mailpref/pgsql-performance [2] > > > > Links: > ------ > [1] > https://lists.postgresql.org/mj/mj_wwwusr/domain=postgresql.org/debasis.moharana%40ipathsolutions.co.in > [2] http://www.postgresql.org/mailpref/pgsql-performance > [3] https://www.postgresql.org/docs/current/static/sql-explain.html > [4] https://explain.depesz.com/ Hi, Please check the execution plan details Execution Query is = EXPLAIN (ANALYZE, BUFFERS) select * from tblPurchaseOrderstock cross join tblPurchaseOrderInfo; "Nested Loop (cost=0.00..507.51 rows=39593 width=224) (actual time=0.032..13.026 rows=39593 loops=1)" " Buffers: shared read=8" " I/O Timings: read=0.058" " -> Seq Scan on tblpurchaseorderstock (cost=0.00..7.89 rows=289 width=95) (actual time=0.014..0.082 rows=289 loops=1)" " Buffers: shared read=5" " I/O Timings: read=0.040" " -> Materialize (cost=0.00..5.05 rows=137 width=129) (actual time=0.000..0.006 rows=137 loops=289)" " Buffers: shared read=3" " I/O Timings: read=0.019" " -> Seq Scan on tblpurchaseorderinfo (cost=0.00..4.37 rows=137 width=129) (actual time=0.011..0.035 rows=137 loops=1)" " Buffers: shared read=3" " I/O Timings: read=0.019" "Planning time: 56.052 ms" "Execution time: 14.038 ms" Regards, Debasis Moharana -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance