| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Olivier Leprêtre <o(dot)lepretre(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Track pgsql steps |
| Date: | 2020-07-29 17:58:09 |
| Message-ID: | 42850458-0e48-cad2-4c89-34296a6f0383@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
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
>
> Thanks,
>
> Olivier
>
>
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
> Garanti sans virus. www.avast.com
> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>
>
>
> <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Steve Baldwin | 2020-07-29 23:56:35 | Transaction prevention |
| Previous Message | Olivier Leprêtre | 2020-07-29 15:44:58 | Track pgsql steps |