about hacking postgresql

Started by abdelhak benmohamedalmost 17 years ago2 messages
#1abdelhak benmohamed
abdelhak.benmohamed@yahoo.fr

hello,
here more of details
I have a set of transaction.  Naturally, the transactions execute themselves in competition.  But I would want to give to every transaction a priority. Thus the transaction more priority must execute itself in first. 
 
I thought, as first step, to change the transaction syntax as follows
Start transaction (priority)
 
But I do not know where to do exactly the change in gram.y
for I have to try to change in TransactionStmt, but I always receive the message syntax error at now near (
 
thanks you a lot
 

#2Hans-Juergen Schoenig
postgres@cybertec.at
In reply to: abdelhak benmohamed (#1)
Re: about hacking postgresql

abdelhak benmohamed wrote:

hello,

here more of details

I have a set of transaction. Naturally, the transactions execute
themselves in competition. But I would want to give to every
transaction a priority. Thus the transaction more priority must
execute itself in first.

I thought, as first step, to change the transaction syntax as follows

Start transaction (priority)

But I do not know where to do exactly the change in gram.y

for I have to try to change in TransactionStmt, but I always receive
the message syntax error at now near (

thanks you a lot

hello ...

if you pump then in through the same database connection you do
basically the same thing.
if you want transactions to lock out each other, take a look at advisory
locks.
implementing this for "start transaction" seems pretty useless to me
however.

best regards,

hans

--
Cybertec Sch�nig & Sch�nig GmbH
Professional PostgreSQL Consulting, Support, Training
Gr�hrm�hlgasse 26, A-2700 Wiener Neustadt
Web: www.postgresql-support.de