Received: from smtp3.erols.com (smtp3.erols.com [207.172.3.236]) by hub.org (8.8.8/8.7.5) with ESMTP id MAA04126 for ; Fri, 21 Aug 1998 12:23:45 -0400 (EDT) Received: from erols.com (207-172-120-71.s71.tnt14.brd.erols.com [207.172.120.71]) by smtp3.erols.com (8.8.8/8.8.5) with ESMTP id MAA24932; Fri, 21 Aug 1998 12:23:42 -0400 (EDT) Sender: fred@erols.com Message-ID: <35DD9FAA.52C4F900@erols.com> Date: Fri, 21 Aug 1998 12:26:18 -0400 From: "Fred C. Richards" Organization: Dynamic Software Solutions X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.35 i586) MIME-Version: 1.0 To: pgsql-sql@postgresql.org Subject: Implementing transactions (reference) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit I would like to learn some more about how transactions are implemented in SQL databases, specifically about what goes on behind the scene when you start a new transactions, do some operations, and finally commit the operations. In particular, I'd like to understand how the database programmers make this happen. It seems like every transaction requires a "parallel reality" for the database until it is finally committed. Is there some definitive database textbook that addresses this topic that would help an inquisitive person (and experienced programmer) understand what's going on behind the scenes? Does PostgreSQL follow the canonical standard? Where in the code would I start looking to understand this better? -Fred