On Wed, Apr 25, 2012 at 12:52 PM, Venki Ramachandran <
venki_ramachand...@yahoo.com> wrote:
>
> Now I have to run the same pgplsql on all possible combinations of
> employees and with 542 employees that is about say 300,000 unique pairs.
>
> So (30 * 40)/(1000 * 60 * 60) = 3.33 hours and I hav
On 2012-04-26 04:40, Venki Ramachandran wrote:
Thanks Tom, clock_timestamp() worked. Appreciate it!!! and Sorry was
hurrying to get this done at work and hence did not read through.
Can you comment on how you would solve the original problem? Even if I
can get the 11 seconds down to 500 ms fo
On Wed, Apr 25, 2012 at 12:52 PM, Venki Ramachandran <
venki_ramachand...@yahoo.com> wrote:
> Hi all:
> Can someone please guide me as to how to solve this problem? If this is
> the wrong forum, please let me know which one to post this one in. I am new
> to Postgres (about 3 months into it)
>
> I
Stehule ; Samuel Gendler
; "pgsql-performance@postgresql.org"
Sent: Wednesday, April 25, 2012 2:52 PM
Subject: Re: [PERFORM] Parallel Scaling of a pgplsql problem
Venki Ramachandran writes:
> Replacing current_timestamp() with transaction_timestamp()
> and statement_timestam
On Wed, Apr 25, 2012 at 1:52 PM, Venki Ramachandran
wrote:
> Hi all:
> Can someone please guide me as to how to solve this problem? If this is the
> wrong forum, please let me know which one to post this one in. I am new to
> Postgres (about 3 months into it)
>
> I have PostGres 9.0 database in a
Venki Ramachandran writes:
> Replacing current_timestamp() with transaction_timestamp()
> and statement_timestamp() did not help!!!.
You did not read the documentation you were pointed to. Use
clock_timestamp().
regards, tom lane
--
Sent via pgsql-performance mailing
h will tell me where the 11 seconds is being
spent. How do I do that?
Thanks, Venki
From: Pavel Stehule
To: Venki Ramachandran
Cc: Samuel Gendler ;
"pgsql-performance@postgresql.org"
Sent: Wednesday, April 25, 2012 2:26 PM
Subject: Re:
ages should be inserted or not, 0=insert, 1 = do_not_insert.
> When I toggle the flag the overall timing did not change. Does it not some
> time in ms to write 3832 rows to a table?
> Why is my current_timestamp value not changing. I was expecting the
> difference between the last row's
mestamp value not changing. I was expecting the difference
between the last row's timestamp value MINUS the first row's tiemstamp value to
equal my 11.685 seconds. What is wrong here?
-Venki
From: Samuel Gendler
To: Venki Ramachandran
Cc: "pgsql-
Hello
2012/4/25 Venki Ramachandran :
> Hi all:
> Can someone please guide me as to how to solve this problem? If this is the
> wrong forum, please let me know which one to post this one in. I am new to
> Postgres (about 3 months into it)
>
> I have PostGres 9.0 database in a AWS server (x-large) a
Venki Ramachandran wrote:
> I have PostGres 9.0 database in a AWS server (x-large) and a
> pgplsql program that does some computation. It takes in a date
> range and for one pair of personnel (two employees in a company)
> it calculates some values over the time period. It takes about
> 40ms (mi
On Wed, Apr 25, 2012 at 11:52 AM, Venki Ramachandran <
venki_ramachand...@yahoo.com> wrote:
> Hi all:
> Can someone please guide me as to how to solve this problem? If this is
> the wrong forum, please let me know which one to post this one in. I am new
> to Postgres (about 3 months into it)
>
> I
Hi all:
Can someone please guide me as to how to solve this problem? If this is the
wrong forum, please let me know which one to post this one in. I am new to
Postgres (about 3 months into it)
I have PostGres 9.0 database in a AWS server (x-large) and a pgplsql program
that does some computatio
13 matches
Mail list logo
