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
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 for one pair, running it for 300k pairs will take
On 04/23/2012 10:56 PM, Jan Nielsen wrote:
We are planning to rebuild our production 50GB PG 9.0 database serving
our application platform on the new hardware below. The web-applications
are 80/20 read/write and the data gateways are even mix 50/50
read/write; one of the gateways nightly exports
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
Replacing current_timestamp() with transaction_timestamp()
and statement_timestamp() did not help!!!.
My timestamp values are still the same. I can't believe this is not possible in
PG. In oracle you can use 'select sysdate from dual' and insert that value and
you can see which sql statement
On 04/25/2012 02:46 AM, John Lister wrote:
Hi, I'd be grateful if you could share any XFS performance tweaks as I'm
not entirely sure I'm getting the most out of my setup and any
additional guidance would be very helpful.
Ok, I'll give this with a huge caveat: these settings came from lots of
Hello
http://www.postgresql.org/docs/8.1/static/functions-datetime.html
CURRENT_TIME and CURRENT_TIMESTAMP deliver values with time zone;
LOCALTIME and LOCALTIMESTAMP deliver values without time zone.
CURRENT_TIME, CURRENT_TIMESTAMP, LOCALTIME, and LOCALTIMESTAMP can
optionally take a precision
Another question (probably a silly mistake) while debugging this problem:
I put in insert statements into the pgplsql code to collect the
current_timestamp and see where the code was spending most of it timeThe
output is as follows:
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
On Wed, Apr 25, 2012 at 7:08 PM, Greg Sabino Mullane wrote:
>> Is it established practice in the Postgres world to separate indexes
>> from tables? I would assume that the reasoning of Richard Foote -
>> albeit for Oracle databases - is also true for Postgres:
>
> Yes, it's an established practi
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
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> Is it established practice in the Postgres world to separate indexes
> from tables? I would assume that the reasoning of Richard Foote -
> albeit for Oracle databases - is also true for Postgres:
Yes, it's an established practice. I'd call i
16 matches
Mail list logo
