Please, read chapter 43.10.1 of the PostgreSQL documentation (https://www.postgresql.org/docs/11/plpgsql-trigger.html <https://www.postgresql.org/docs/11/plpgsql-trigger.html>). Just to be sure we are on the same page.
> On 28. Feb 2020, at 14:59, stan <st...@panix.com> wrote: > > On Thu, Feb 27, 2020 at 10:30:15PM +0100, Andrei Zhidenkov wrote: >> Why not to pass TG_TABLE_SCHEMA and TG_TABLE_NAME in its arguments? >> >>> On 27. Feb 2020, at 22:28, stan <st...@panix.com> wrote: >>> >>> I ma considering setting up a function, and triggers to put a record in an >>> audit table when certain tables are altered. I pretty much think I know how >>> to do this, with one exception. >>> >>> Can a function, called by a trigger, determine what table it was called >>> for? >>> > > I suppose I could do that. I have in mind a single function to accomplish the > audit log, but I will have to have unique triggers for each table. I was > just hoping not to have to do that. Are these values that I could read > automatically? Or do I have to hard code them? > > -- > "They that would give up essential liberty for temporary safety deserve > neither liberty nor safety." > -- Benjamin Franklin
