agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedFrom: MARCIN JANUCHTA (P.445) <MARTIN@kastor.ics.tup.edu.pl>
To: postgres@postgres.Berkeley.EDU
Cc: martin@pozn1v.tup.edu.pl
Cc: martin@kastor.ics.tup.edu.pl
Subject: concurrency control structures in Postgres
Date: Fri, 22 Apr 1994 13:15:32 CET-0
Message-ID: <BA9B9A4047@kastor.ics.tup.edu.pl> (raw)
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
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: postgres@postgres.berkeley.edu
Cc: MARTIN@kastor.ics.tup.edu.pl, martin@pozn1v.tup.edu.pl
Subject: Re: concurrency control structures in Postgres
In-Reply-To: <BA9B9A4047@kastor.ics.tup.edu.pl>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox