Received: from magus.postgresql.org (magus.postgresql.org [87.238.57.229]) by mail.postgresql.org (Postfix) with ESMTP id EB1DC1E64F42 for ; Sun, 27 Nov 2011 13:17:14 -0400 (AST) Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RUiLo-0004i0-6F for pgsql-sql@postgresql.org; Sun, 27 Nov 2011 17:17:13 +0000 Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.2/8.14.2) with ESMTP id pARHGvOx024014; Sun, 27 Nov 2011 12:16:57 -0500 (EST) To: Belinda Cussen cc: Pavel Stehule , pgsql-sql@postgresql.org Subject: Re: Does anyone know of any issues around ARRAY UNNEST In-reply-to: References: Comments: In-reply-to Belinda Cussen message dated "Fri, 25 Nov 2011 08:09:43 +1100" Date: Sun, 27 Nov 2011 12:16:57 -0500 Message-ID: <24013.1322414217@sss.pgh.pa.us> From: Tom Lane X-Pg-Spam-Score: -3.1 (---) X-Archive-Number: 201111/83 X-Sequence-Number: 36056 Belinda Cussen writes: > The code works ok on my database too when I call the procedure only once > sequentially. I hit the segmentation fault consistently when I try to call > the proc concurrently. What do you mean by "concurrently"? There is no multithreading within Postgres backends, and it's really hard to believe that unnest would be affected by what's happening in other server processes. regards, tom lane