Re: [HACKERS] Transactions ...

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: The Hermit Hacker <scrappy(at)hub(dot)org>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: [HACKERS] Transactions ...
Date: 1999-12-14 20:11:58
Message-ID: 16139.945202318@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

The Hermit Hacker <scrappy(at)hub(dot)org> writes:
> and the following being pumped out of hte backend (have debug mode's

> StartTransactionCommand^M
> query: BEGIN WORK^M
> ProcessUtility: BEGIN WORK^M
> CommitTransactionCommand^M
> StartTransactionCommand^M
> query: INSERT INTO dict (url_id,word,intag) VALUES(810,'date',3)^M
> ProcessQuery^M
> CommitTransactionCommand^M
> StartTransactionCommand^M

> If they issue a 'BEGIN WORK', shouldn't it eliminate all the
> '{Commit,Start}TransactionCommand's?

No. Those routines are still called, they just behave differently.

You're not the first one to be confused by those debug messages, IIRC.
It would probably make sense to rip those TPRINTFs out of postgres.c,
which only knows that it's calling those 2 routines, and put TPRINTFs
into the routines themselves (in xact.c) that show what state transition
is actually being taken...

regards, tom lane

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 1999-12-14 20:14:15 Re: [HACKERS] [6.5.3] FATAL 1: my bits moved right off the end of the world!
Previous Message Peter Eisentraut 1999-12-14 19:26:33 Arrays