Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WWATT-0006EV-GJ for pgsql-performance@arkaria.postgresql.org; Fri, 04 Apr 2014 20:12:27 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.80) (envelope-from ) id 1WWATS-0002IZ-Oc for pgsql-performance@arkaria.postgresql.org; Fri, 04 Apr 2014 20:12:26 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WWAOU-0002Bq-0O for pgsql-performance@postgresql.org; Fri, 04 Apr 2014 20:07:18 +0000 Received: from mail-wg0-x231.google.com ([2a00:1450:400c:c00::231]) by magus.postgresql.org with esmtp (Exim 4.80) (envelope-from ) id 1WWAOR-0004qZ-F3 for pgsql-performance@postgresql.org; Fri, 04 Apr 2014 20:07:17 +0000 Received: by mail-wg0-f49.google.com with SMTP id a1so4019132wgh.20 for ; Fri, 04 Apr 2014 13:07:12 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=ah7roXBZWP1SEVuNBb2G+A6sRDsuSuriL3KDG6jRpzs=; b=MsV+2QZNRUG0sQCshkfdkR49co1bcyl1MuTDGA6Y0+MQNQeIaqSWPYO+s+dJmplJ9E Z9nZK0YjuT8tBP0eMxNoM42xO2IQ/N7/f/RdMTWj3h43cRXyW8UD8744Pdpifp/kWau1 GgVleHjGND2W5XrZL8ykONyqKxvDp4ISmGlMZ1b4LBO3GHI3cs/TNWkWEWYPiuLr+zNQ HVN2DnBWhLbcZRsKdn55Wsih+nn7pN0vimr6PxSM31RwOmh4chCctjWjgze5nTRxYBTK JuYnQ18Y0ofm9UMQs7JvcHsNcz+/92quFMh8395c8Lp3Gf/SKM38QJau5hi3MkcDTgjI J9Hw== X-Received: by 10.180.96.200 with SMTP id du8mr7125341wib.43.1396642032560; Fri, 04 Apr 2014 13:07:12 -0700 (PDT) Received: from [192.168.1.30] (96.84.15.109.rev.sfr.net. [109.15.84.96]) by mx.google.com with ESMTPSA id gi8sm301025wib.8.2014.04.04.13.07.11 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 04 Apr 2014 13:07:11 -0700 (PDT) Message-ID: <533F10E6.4010303@gmail.com> Date: Fri, 04 Apr 2014 22:07:02 +0200 From: PARIS Nicolas User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Thom Brown CC: pgsql-performance Subject: Re: PGSQL 9.3 - Materialized View - multithreading References: <533F0CB8.40001@gmail.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit X-Pg-Spam-Score: -2.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 Ok thanks, And what about triggers. 8 triggers based on the same event won't be multithreaded ? Le 04/04/2014 21:57, Thom Brown a écrit : > On 4 April 2014 20:49, PARIS Nicolas wrote: >> Thanks, >> >> "The only thing that immediately comes to mind would be running a >> rather hacky DO function in 4 separate sessions:" >> You mean 8 sessions I guess. > > Yes, typo. > >> 8 separate sessions ? >> Have you any idea how to manage sessions ? Is it possible to create >> separate session internaly ? >> Do I have to make 8 external connection to database, to get 8 process. >> It would be great if I could manage session internaly, in a pl/sql by >> example. > > Well you can't have multiple sessions per connection, so yes, you'd > need to issue each of them in separate connections. > > I can't think of a more convenient way of doing it, but the solution > I've proposed isn't particularly elegant anyway. > -- Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-performance