Received: from talshiar.kja-essen.de (root@[193.158.244.43]) by hub.org (8.9.3/8.9.3) with ESMTP id LAA57291 for ; Sat, 2 Oct 1999 11:34:34 -0400 (EDT) (envelope-from wn@kja-essen.de) Received: from kja-essen.de (dialin.kja-essen.de [193.158.244.35]) by talshiar.kja-essen.de (8.9.3/8.9.3/Debian/GNU/woho) with ESMTP id QAA09539; Wed, 25 Aug 1999 16:11:27 +0200 Sender: wn@kja-essen.de Message-ID: <37F62577.43286F68@kja-essen.de> Date: Sat, 02 Oct 1999 17:32:07 +0200 From: Wolfgang Hottgenroth Reply-To: woho@ieee.org X-Mailer: Mozilla 4.5 [en] (X11; I; Linux 2.2.12 i486) X-Accept-Language: en MIME-Version: 1.0 To: Thomas Lockhart CC: woho@ieee.org, pgsql-interfaces@hub.org Subject: Re: [INTERFACES] problems with large-objects References: <37F5B8DD.68DB625F@kja-essen.de> <37F61F8E.FEF2A538@alumni.caltech.edu> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Hi Thomas, hi all, Thomas Lockhart wrote: > > > did anyone of you ever saw some strange problems with large objects and > > the postgresql 6.51? > > I don't work with Large Objects, but I am pretty sure that the > behavior was changed/fixed for v6.5 to *require* all large object > manipulation to happen within a transaction. This was always a > requirement, but Postgres did not enforce it and had some potentially > bad behavior lurking as a result. Have many thanks for that fast answer. It is new to me, that large-object-operations requires transactions. Did I read the manual to fast or isn't it written down there? I will try it. Wolfgang