Received: from makus.postgresql.org (makus.postgresql.org [98.129.198.125]) by mail.postgresql.org (Postfix) with ESMTP id 2D67DCE2ABE for ; Sat, 21 Jan 2012 02:34:17 -0400 (AST) Received: from 2605ds1-ynoe.0.fullrate.dk ([90.184.12.24] helo=shrek.krogh.cc) by makus.postgresql.org with esmtp (Exim 4.72) (envelope-from ) id 1RoUWm-0003w0-Pa for pgsql-admin@postgresql.org; Sat, 21 Jan 2012 06:34:17 +0000 Received: from localhost (localhost [127.0.0.1]) by shrek.krogh.cc (Postfix) with ESMTP id 041F3C44780 for ; Sat, 21 Jan 2012 07:34:03 +0100 (CET) X-Virus-Scanned: Debian amavisd-new at shrek.krogh.cc Received: from shrek.krogh.cc ([127.0.0.1]) by localhost (shrek.krogh.cc [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kpnKji5H4UdH for ; Sat, 21 Jan 2012 07:33:59 +0100 (CET) Received: from [90.184.13.151] (2605ds1-ynoe.2.fullrate.dk [90.184.13.151]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: jesper@krogh.cc) by shrek.krogh.cc (Postfix) with ESMTPSA id BB784C44771 for ; Sat, 21 Jan 2012 07:33:59 +0100 (CET) Message-ID: <4F1A5C57.1010605@krogh.cc> Date: Sat, 21 Jan 2012 07:33:59 +0100 From: Jesper Krogh User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.17) Gecko/20110424 Thunderbird/3.1.10 MIME-Version: 1.0 To: pgsql-admin@postgresql.org Subject: Force explicit transactions on insert / update Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Pg-Spam-Score: 0.8 (/) X-Archive-Number: 201201/123 X-Sequence-Number: 39035 Hi. Is there any way I can force explicit use of transactions on insert/updates? I do have users sitting on the system, that may forget to code it that way and it would be nice to be able to force the database to just kick them out if it didn't happen. -- Jesper