Re: isolationtester - allow a session specific connection string

From: Peter Smith <smithpb2250(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: isolationtester - allow a session specific connection string
Date: 2022-12-19 06:35:14
Message-ID: CAHut+Pvc6igoRwBFEqBk1sM2uPWtxSFxOHEjboM2kb9qZTD5kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Dec 19, 2022 at 5:04 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Peter Smith <smithpb2250(at)gmail(dot)com> writes:
> > My patch/idea makes a small change to the isolationtester spec
> > grammar. Now each session can optionally specify its own connection
> > string. When specified, this will override any connection string for
> > that session that would otherwise have been used. This is the only
> > change.
>
> Surely this cannot work, because isolationtester only runs one
> monitoring session. How will it detect wait conditions for
> sessions connected to some other postmaster?
>

You are right - probably it can't work in a generic sense. But if the
"controller session" (internal session 0) is also configured to use
the same conninfo as all my "publisher" sessions (the current patch
can't do this but it seems only a small change) then all of the
publisher-side sessions will be monitored like they ought to be --
which is all I really needed I think.

------
Kind Regards,
Peter Smith
Fujitsu Australia

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2022-12-19 06:53:14 Re: pg_upgrade allows itself to be run twice
Previous Message Michael Paquier 2022-12-19 06:22:59 Re: [PATCH] Teach pg_waldump to extract FPIs from the WAL