Received: from sss.pgh.pa.us ([192.204.191.242]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f650csa23128 for ; Wed, 4 Jul 2001 20:38:54 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.4/8.11.4) with ESMTP id f650cPJ01520; Wed, 4 Jul 2001 20:38:25 -0400 (EDT) To: =?iso-8859-1?Q?DI_Hasen=F6hrl?= cc: pgsql-sql@postgresql.org Subject: Re: Kind of error-handler in a pgsql function In-reply-to: <00c401c104c0$b9a03200$01011eac@irina> References: <00c401c104c0$b9a03200$01011eac@irina> Comments: In-reply-to =?iso-8859-1?Q?DI_Hasen=F6hrl?= message dated "Wed, 04 Jul 2001 21:37:13 +0200" Date: Wed, 04 Jul 2001 20:38:25 -0400 Message-ID: <1517.994293505@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200107/41 X-Sequence-Number: 3822 =?iso-8859-1?Q?DI_Hasen=F6hrl?= writes: > I want to know the result of an insert or update, because I call these func= > tions from an Access form and the next steps of the program depend on these= > results. See the FOUND variable (if you just want to test zero or not-zero rows processed) or the SET DIAGNOSTICS statement to get the row count. There is no way to trap an error inside a plpgsql function, however. regards, tom lane