Received: from malur.postgresql.org ([217.196.149.56])
	by arkaria.postgresql.org with esmtp (Exim 4.72) (envelope-from
	<pgsql-sql-owner+M36998=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1ToQbI-0007hO-Qd
	for pgsql-sql@arkaria.postgresql.org; Fri, 28 Dec 2012 03:27:13 +0000
Received: from localhost ([127.0.0.1] helo=postgresql.org)
	by malur.postgresql.org with smtp (Exim 4.72) (envelope-from
	<pgsql-sql-owner+M36998=pgsql+2Dsql=arkaria.postgresql.org@postgresql.org>)
	id 1ToQbH-0003fS-Oy
	for pgsql-sql@arkaria.postgresql.org; Fri, 28 Dec 2012 03:27:11 +0000
Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29])
	by malur.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <msi77@yandex.ru>) id 1ToQb8-0003Xz-HF
	for pgsql-sql@postgresql.org; Fri, 28 Dec 2012 03:27:02 +0000
Received: from forward19.mail.yandex.net ([2a02:6b8:0:1402::4])
	by magus.postgresql.org with esmtp (Exim 4.72)
	(envelope-from <msi77@yandex.ru>) id 1ToQb6-0001rN-BF
	for pgsql-sql@postgresql.org; Fri, 28 Dec 2012 03:27:02 +0000
Received: from web3g.yandex.ru (web3g.yandex.ru [95.108.252.103])
	by forward19.mail.yandex.net (Yandex) with ESMTP id AE2281122103;
	Fri, 28 Dec 2012 07:26:56 +0400 (MSK)
Received: from 127.0.0.1 (localhost.localdomain [127.0.0.1])
	by web3g.yandex.ru (Yandex) with ESMTP id 608451A98001;
	Fri, 28 Dec 2012 07:26:56 +0400 (MSK)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail;
	t=1356665216; bh=NoiuYFsEaQAZBVvi4igeYqQWLO8prFZW4xalYLOA53k=;
	h=From:To:Cc:In-Reply-To:References:Subject:Date;
	b=Kimspt2cEaqW+t9IBuLbWwCdRQGw+ydx6vjSk37yIl8oLU8RIlil4mrVb2QyPobTL
	+2+b67/hm5hAplQuIpDYYiHW2SPtwrOOcAvZWZa8yyE3JG8Mtj+duhDRgMWdjKVFGT
	GlBIHpgKGoMCZmRsPHEjHBVB6dgBpQ85puOK5MOw=
Received: from [2.94.103.18] ([2.94.103.18]) by web3g.yandex.ru with HTTP;
	Fri, 28 Dec 2012 07:26:56 +0400
From: msi77 <msi77@yandex.ru>
To: "johnf@jfcomputer.com" <johnf@jfcomputer.com>
Cc: pgsql-sql@postgresql.org
In-Reply-To: <50DC5AD0.3040507@jfcomputer.com>
References: <50DC5AD0.3040507@jfcomputer.com>
Subject: Re: strange corruption?
MIME-Version: 1.0
Message-Id: <2670191356665216@web3g.yandex.ru>
X-Mailer: Yamail [ http://yandex.ru ] 5.0
Date: Fri, 28 Dec 2012 07:26:56 +0400
Content-Type: text/plain; charset=koi8-r
Content-Transfer-Encoding: quoted-printable
X-Pg-Spam-Score: -1.5 (-)
List-Archive: <http://archives.postgresql.org/pgsql-sql>
List-Help: <mailto:majordomo@postgresql.org?body=help>
List-ID: <pgsql-sql.postgresql.org>
List-Owner: <mailto:pgsql-sql-owner@postgresql.org>
List-Post: <mailto:pgsql-sql@postgresql.org>
List-Subscribe: <mailto:majordomo@postgresql.org?body=sub%20pgsql-sql>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-sql>
X-Mailing-List: pgsql-sql
Precedence: bulk
Sender: pgsql-sql-owner@postgresql.org

Hi,
Maybe you have triggers on the target table.

27.12.2012, 18:28, "John Fabiani" <johnf@jfcomputer.com>:
> Hi,
> I have the following statement in a function.
>
> =9A=9A=9A=9A=9AUPDATE orderseq
> =9A=9A=9A=9A=9ASET orderseq_number =3D (orderseq_number + 1)
> =9A=9A=9A=9A=9AWHERE (orderseq_name=3D'InvcNumber');
>
> All it does is update a single record by incrementing a value (int).
>
> But it never completes. =9AThis has to be some sort of bug. =9AAnyone hav=
e a
> thought what would cause this to occur. =9ATo my knowledge it was working
> and does work in other databases.
>
> Johnf
>
> --
> Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-sql


--=20
Sent via pgsql-sql mailing list (pgsql-sql@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-sql