From: | Souvik Bhattacherjee <kivuosb(at)gmail(dot)com> |
---|---|
To: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
Cc: | "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 19:22:31 |
Message-ID: | CAANrPSckb71-5L-vCpVMHr1mqmDQhzgODj0WZL0B+ZZW+-dHxA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
> It would help to know what problem you are trying to solve?
Multiple txns are inserting tuples into a table concurrently. Wanted to
measure
the total time taken to complete the insertion process. Some txns overlap
with
others on the tuples they insert. Duplicate tuples are not inserted.
On Wed, Jul 24, 2019 at 1:58 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
wrote:
> On 7/24/19 9:54 AM, Souvik Bhattacherjee wrote:
> > Hi,
> >
> > Is there a standard procedure to execute two or more concurrent txns at
> > the same time? I understand that if we want to run concurrent txns, we
> > need to execute them from different psql sessions. But how do we make
> > sure that they begin execution almost at the same time.
>
> Well different sessions be they psql or some other client. That would be
> the difficulty, determining what is submitting the transaction.
>
> >
> > Also, I'm interested in measuring the time taken across all executing
> > txns, i.e. the time from the start of the earliest txns till the end of
> > the last txn.
>
> It would help to know what problem you are trying to solve?
>
> >
> > Best,
> > -SB
>
>
> --
> Adrian Klaver
> adrian(dot)klaver(at)aklaver(dot)com
>
From | Date | Subject | |
---|---|---|---|
Next Message | Imre Samu | 2019-07-24 19:23:16 | Re: partition table slow planning |
Previous Message | Adrian Klaver | 2019-07-24 19:05:41 | Re: Too slow to create new schema and their tables, functions, triggers. |