Skip site navigation (1) Skip section navigation (2)

Re: Parallel Scaling of a pgplsql problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Venki Ramachandran <venki_ramachandran(at)yahoo(dot)com>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Samuel Gendler <sgendler(at)ideasculptor(dot)com>, "pgsql-performance(at)postgresql(dot)org" <pgsql-performance(at)postgresql(dot)org>
Subject: Re: Parallel Scaling of a pgplsql problem
Date: 2012-04-25 21:52:08
Message-ID: 5452.1335390728@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-performance
Venki Ramachandran <venki_ramachandran(at)yahoo(dot)com> writes:
> Replacing current_timestamp() withtransaction_timestamp() andstatement_timestamp() did not help!!!.

You did not read the documentation you were pointed to.  Use
clock_timestamp().

			regards, tom lane

In response to

Responses

pgsql-performance by date

Next:From: Merlin MoncureDate: 2012-04-25 22:05:43
Subject: Re: Parallel Scaling of a pgplsql problem
Previous:From: Venki RamachandranDate: 2012-04-25 21:45:38
Subject: Re: Parallel Scaling of a pgplsql problem

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group