Return-Path: owner-postman Delivery-Date: Fri, 22 Apr 94 09:26:12 -0700 Return-Path: owner-postman Received: from localhost (localhost [127.0.0.1]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with SMTP id EAA23813 for postgres-redist; Fri, 22 Apr 1994 04:17:41 -0700 Resent-From: POSTGRES mailing list Resent-Message-Id: <199404221117.EAA23813@nobozo.CS.Berkeley.EDU> X-Authentication-Warning: nobozo.CS.Berkeley.EDU: Host localhost didn't use HELO protocol Sender: owner-postman@postgres.Berkeley.EDU X-Return-Path: owner-postman Received: from sunic.sunet.se (sunic.sunet.se [192.36.125.2]) by nobozo.CS.Berkeley.EDU (8.6.4/8.6.3) with ESMTP id EAA23804 for ; Fri, 22 Apr 1994 04:17:32 -0700 Received: from cocos.fuw.edu.pl by sunic.sunet.se (8.6.8/2.03) id NAA12095; Fri, 22 Apr 1994 13:17:06 +0200 Received: from perseus.tup.edu.pl by cocos.fuw.edu.pl (4.1/SMI-4.1) id AA27718; Fri, 22 Apr 94 13:16:51 +0200 Received: from kastor.ics.tup.edu.pl by perseus.tup.edu.pl id aa08837; Fri, 22 Apr 94 18:14:13 MET Received: from KASTOR/MAILQUEUE by kastor.ics.tup.edu.pl (Mercury 1.1); Fri, 22 Apr 94 13:16:05 CET-0 From: "MARCIN JANUCHTA (P.445)" To: postgres@postgres.Berkeley.EDU Date: Fri, 22 Apr 1994 13:15:32 CET-0 Subject: concurrency control structures in Postgres Cc: martin@pozn1v.tup.edu.pl, martin@kastor.ics.tup.edu.pl Priority: normal X-Mailer: PMail v3.0 (R1a) Message-Id: Resent-To: postgres-redist@postgres.Berkeley.EDU Resent-Date: Fri, 22 Apr 94 04:17:40 -0700 Resent-XMts: smtp I am supervising a project in extending Postgres to handle complex event detection, monitoring other systems (like Oracle and Novell netware) etc. It would be very valuable to provide a real-time support for these tasks. First of all I need to adjust the concurrency control to be priority sensitive. Does anybody have the documentation concerning the lock table structure and lock request/grant routines in Postgres code, as well as the internal representation of transactions? It is also very important to be able to abort a chosen transaction by calling some "abort" function. I hope that somebody (perhaps from the Postgres team) would be so kind to enlighten me (if it's not a kind of trade secret...). The documentation coming with the 4.1 or 4.2 does not cover the subject (except few lines at the end of am.ps). Thank you very much in advance for your kind consideration. Regards, Marcin Januchta (martin@kastor.ics.tup.edu.pl, @pozn1v.tup.edu.pl) Institute of Computing Science Poznan Technical University Poznan, Poland