Trouble with plpgsql generic trigger function using special variables - Mailing list pgsql-general

From Lenorovitz, Joel
Subject Trouble with plpgsql generic trigger function using special variables
Date
Msg-id 7119BB016BDF6445B20A4B9F14F50B2D44A8AC@WILSON.usap.gov
Whole thread Raw
Responses Re: Trouble with plpgsql generic trigger function using  (Richard Huxton <dev@archonet.com>)
Re: Trouble with plpgsql generic trigger function using  (Alban Hertroys <alban@magproductions.nl>)
List pgsql-general
I'd like to create a trigger function whose use can extend to multiple
tables by employing the special variables available (e.g., TG_RELNAME).
Below is a simple version of such a function that ought to prevent
insertion of greater than 4 total records in the table that calls it.
I'm not sure that I'm using or dereferencing the trigger variables
correctly, however, particularly in the query.  I have tried many
syntax, type casting, and alternate variable assignment variations, but,
aside from parsing successfully, this code does not seem to work as
intended.    Can somebody correct this specific example to have it work
properly and/or further explain how to use these variables?  Any advice
on outputting the values of the variables to the console for inspection
during testing would be welcome as well (RAISE EXCEPTION doesn't allow a
variable value in the message string, plus it seems a little harsh).

Thanks,
JL

CREATE OR REPLACE FUNCTION trigger_fxn() RETURNS TRIGGER AS $$
    BEGIN
        IF ((TG_OP = 'INSERT') AND (TG_WHEN = 'BEFORE')) THEN
            IF (SELECT COUNT(*) FROM text(TG_RELNAME)) < 4
THEN
                RETURN NEW;
            ELSE
                RETURN NULL;
            END IF;
        END IF;
    END;
$$ LANGUAGE plpgsql;

CREATE TRIGGER test_bi BEFORE INSERT ON test
    FOR EACH ROW EXECUTE PROCEDURE trigger_fxn();

pgsql-general by date:

Previous
From: Andrew Sullivan
Date:
Subject: Re: Pgsql on Solaris
Next
From: Ron Johnson
Date:
Subject: Re: RAM Based Disk Drive?