Re: Track pgsql steps

From: Julien Rouhaud <rjuju123(at)gmail(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
Cc: Olivier Leprêtre <o(dot)lepretre(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Track pgsql steps
Date: 2020-07-30 10:18:45
Message-ID: CAOBaU_Ze2sTDZBRt=xaT6YLj0BXSBmy0L5C1es5nT2VDPS9U-Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Wed, Jul 29, 2020 at 7:58 PM Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> wrote:
>
> On 7/29/20 8:44 AM, Olivier Leprêtre wrote:
> > Hi,
> >
> > I have a rather long pgsql procedure and I would like to detect which
> > step is currently executing (subscript 1,2,3…). Due to transaction
> > isolation, it’s not possible to make it write in a table or get nexval
> > from a sequence because values become available only after the complete
> > end of the procedure.
> >
> > Do you see any solution in this purpose ?
>
> RAISE NOTICE?:
>
> https://www.postgresql.org/docs/12/plpgsql-errors-and-messages.html#PLPGSQL-STATEMENTS-RAISE

You can also abuse SET application_name, as the value will be directly
seen by other transactions. You're quite limited in the number of
bytes to use, but if you just need to do some quick testing it can be
helpful.

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Zwettler Markus (OIZ) 2020-07-30 10:33:45 How to find out why user processes are using so much memory?
Previous Message Daniel Westermann (DWE) 2020-07-30 08:57:07 Re: Out of memory with "create extension postgis"