pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Belinda Cussen <belinda.cussen@servian.com.au>
Cc: Pavel Stehule <pavel.stehule@gmail.com>
Cc: pgsql-sql@postgresql.org
Subject: Re: Does anyone know of any issues around ARRAY UNNEST
Date: Sun, 27 Nov 2011 12:16:57 -0500
Message-ID: <24013.1322414217@sss.pgh.pa.us> (raw)
In-Reply-To: <CA+QS4W4u18J4YxHBjpmUX6Gb7EGE31qnf=rEmOVA4ThtLAwZqQ@mail.gmail.com>
References: <CA+QS4W6nCLt46KF5WxC49X5pH5mLCP8QSOwzJs+tKzxSQvnx2w@mail.gmail.com>
	<CAFj8pRCRUtQrrdYZEAyMRs-T2GrkKXj8uoNF6_WPJPf_B4JaGQ@mail.gmail.com>
	<CA+QS4W4u18J4YxHBjpmUX6Gb7EGE31qnf=rEmOVA4ThtLAwZqQ@mail.gmail.com>

Belinda Cussen <belinda.cussen@servian.com.au> 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



view thread (8+ messages)  latest in thread

Message-ID: <24013.1322414217@sss.pgh.pa.us>
Permalink:  ../24013.1322414217@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/24013.1322414217@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-sql@postgresql.org
  Cc: tgl@sss.pgh.pa.us, belinda.cussen@servian.com.au, pavel.stehule@gmail.com
  Subject: Re: Does anyone know of any issues around ARRAY UNNEST
  In-Reply-To: <24013.1322414217@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox