Re: Running concurrent txns and measuring the timings in Postgres

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: Souvik Bhattacherjee <kivuosb(at)gmail(dot)com>
Cc: Rob Sargent <robjsargent(at)gmail(dot)com>, "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: Running concurrent txns and measuring the timings in Postgres
Date: 2019-07-24 20:44:27
Message-ID: e8eacebb-aaf6-dd5b-cb3a-f5421a069df8@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 7/24/19 1:42 PM, Souvik Bhattacherjee wrote:
> > The duplicate elimination is being handled by ON CONFLICT or some custom
> > process in the code generating the transactions?
>
> Yes, we used ON CONFLICT for that. Thanks btw.
>
> > If the transactions are being created from a single app/script could you
> > not just use 'timing' to mark the beginning of the transactions and the
> > end and record that somewhere(db table and/or file)?
>
> So did you mean to say that I need to get the timestamps of the
> beginning/end
> of the txn since \timing only produces elapsed time?  Surely that would
> solve the
> problem but I'm not sure how to get that done in Postgres.
>
> I wanted to check to see if there are simpler ways to get this done in
> Postgres
> before trying out something similar to Rob's suggestion or yours.
>

Well it depends on the part you have not filled in, what client(s) you
are using and how the transactions are being generated?

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Souvik Bhattacherjee 2019-07-24 20:52:30 Re: Running concurrent txns and measuring the timings in Postgres
Previous Message Souvik Bhattacherjee 2019-07-24 20:42:19 Re: Running concurrent txns and measuring the timings in Postgres