From: | Merlin Moncure <mmoncure(at)gmail(dot)com> |
---|---|
To: | Andy Chambers <achambers(at)mcna(dot)net> |
Cc: | pgsql <pgsql-novice(at)postgresql(dot)org> |
Subject: | Re: Transactions within Function |
Date: | 2012-04-04 17:21:03 |
Message-ID: | CAHyXU0xMBpeoWFSaAGTAZm4dHQ1avWhRaRi=uFAPAqu2jW3M=A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
On Wed, Apr 4, 2012 at 11:17 AM, Andy Chambers <achambers(at)mcna(dot)net> wrote:
> On Wed, Apr 4, 2012 at 12:07 PM, Steve Horn <steve(at)stevehorn(dot)cc> wrote:
>> I have a very basic function that performs several steps. Each one of these
>> steps could take a significant amount of time which I would like to track.
>>
>> To do this I am inserting a record to a logging table with a timestamp.
>> After my function runs, all of my log entries have the exact same timestamp.
>> I am assuming this is because they are all being committed in the same
>> transaction.
>>
>> Is there a way I can commit those log inserts in real time?
>
> Use timeofday() rather than current_time.
>
> http://www.postgresql.org/docs/9.1/static/functions-datetime.html
lately, prefer clock_timestamp(), especially if you need to manipulate
the returned time as a timestamp.
merlin
From | Date | Subject | |
---|---|---|---|
Next Message | Coby Beck | 2012-04-05 00:57:53 | Re: Function returning SETOF returns nothing |
Previous Message | Andy Chambers | 2012-04-04 16:17:53 | Re: Transactions within Function |