Re: Function for Exception Logging - Mailing list pgsql-general

From Tony Shelver
Subject Re: Function for Exception Logging
Date
Msg-id CAG0dhZA3j2sAqm9+9oE_biFojpQ3Y9AR=aGGrBjLCED5csJEGQ@mail.gmail.com
Whole thread Raw
In response to Function for Exception Logging  (Patrick FICHE <Patrick.Fiche@aqsacom.com>)
Responses Re: Function for Exception Logging
List pgsql-general
I'd be interested if there is an answer to this.   The big issue with writing to a table is the interaction with rollbacks and commits.

Even more difficult in PG functions as they have no commit / rollback capability.  I haven't played with stored procedures in in PG11 yet.

In Oracle, I wrote logging / error messages to a logging file on the fire system, directly from PL/SQL.


This file can then be monitored for error messages via a messaging solutions.


Regards



On Mon, 29 Oct 2018 at 19:13, Patrick FICHE <Patrick.Fiche@aqsacom.com> wrote:

Hi community,

 

I would like to implement a function that would log managed Exceptions into a dedicated table.

For example, I have some code like :

BEGIN

Code generation exception

EXCEPTION

  WHEN OTHERS THEN Log_Error();

END;

 

The Log_Error function would be able to get the exception context / parameters to log the exception parameters into a table.

Is there any way to manage this without providing the Exception parameters as parameters to the Log_Error function ?

 

Thanks,

Patrick

 

 

Patrick Fiche

Database Engineer, Aqsacom Sas.

c. 33 6 82 80 69 96

e. patrick.fiche@aqsacom.com

 

01-03_AQSA_Main_Corporate_Logo_JPEG_White_Low.jpg

 

Attachment

pgsql-general by date:

Previous
From: Torsten Förtsch
Date:
Subject: Is there a way to speed up WAL replay?
Next
From: Laurenz Albe
Date:
Subject: Re: Full-text Search - Thesaurus relationships