From: | Alvaro Herrera <alvherre(at)commandprompt(dot)com> |
---|---|
To: | Karen Hill <karen_hill22(at)yahoo(dot)com> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: DTrace and PostgreSQL |
Date: | 2007-04-13 01:08:26 |
Message-ID: | 20070413010826.GA30663@alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Karen Hill wrote:
> I've got Solaris 10 11/06 on my PC. I removed the static keyword in
> src/backend/access/transam/xact.c. for the AbortTransaction and
> CommitTransaction functions declarations and compiled 8.2.3.
> Everything works nicely.
>
> I was wondering if DTrace could tell me how many inserts are being
> done in a pl/pgsql function while in a loop for example. As you know
> a pl/pgsql function executes in a single transaction so the DTrace
> probe "transaction__commit(int)" I believe is not helpful here. Could
> DTrace measure how many inserts are being done in a transaction that
> has not yet been commited, especially if that transaction block is in
> a pl/pgsql function? This would be extremely useful as when one has a
> bunch of inserts one could be able to see how far along the pl/pgsql
> function was.
There are no trace points for that, but you can insert them if you want.
I believe the appropriate place to put it would be either heap_insert or
ExecInsert.
--
Alvaro Herrera http://www.CommandPrompt.com/
The PostgreSQL Company - Command Prompt, Inc.
From | Date | Subject | |
---|---|---|---|
Next Message | raysonlogin@gmail.com | 2007-04-13 01:41:59 | Re: DTrace and PostgreSQL |
Previous Message | Karen Hill | 2007-04-13 00:13:59 | DTrace and PostgreSQL |