Enhance the function trigger__parse.

[lizardoluis]

Add the return variables:
function_name: the procedure name called by the trigger.
table_name: the table which the trigger is associated.

[decibel]

Thanks for the addition! Feel free to just reply to my comments; I can make the necessary changes.

[decibel]

Wouldn't this be better as regprocedure?

[lizardoluis]

Could be!
I followed the name used in the PostgreSQL doc. But its up to you. It was just a suggestion.

[decibel]

Could you describe your use case? I thought about adding this, but presumably if you already know the trigger OID then you already know what table it's on, no?

It should also be regclass instead of text.

[lizardoluis]

What I'm doing is what you helped me to do: http://stackoverflow.com/questions/38212882/postgresql-use-event-trigger-to-validate-a-trigger

The table_name was just a syntax sugar for me. I'm also not that experienced with pgSQL to deal with trigger OID and so. My idea is to use this function you created to parse a trigger and get all information of it. Regclass makes sense though!

I need the function_name to identify which trigger is, so that I can certify that it was created correctly. I wrote some trigger functions that applies some spatial integrity constraints on the database. But each function requires a certain type of trigger (BEFORE, AFTER, STATEMENT, ROW) to be created.

I'll make soon a second commit changing the function_arguments to array. I think its more practical then a string, and more helpful for me, because I need to check the arguments of the function as well.

[decibel]

I need the function_name to identify which trigger is, so that I can certify that it was created correctly. I wrote some trigger functions that applies some spatial integrity constraints on the database. But each function requires a certain type of trigger (BEFORE, AFTER, STATEMENT, ROW) to be created.

If you're trying to find what trigger on a particular table uses a particular trigger function, I think it would be better to have a function that searches for that; something like FUNCTION cat_tools.trigger__get_oids( trigger_table regclass , trigger_function regproc ) RETURNS SETOF oid You could then do SELECT trigger__parse(oid) FROM trigger__get_oids(...) oid

[decibel]

I wanted to do this originally, but this will fail if you have any whitespace in any of the arguments themselves. I don't think it's really worth the (rather considerable) effort it would take to make this fool-proof.

[lizardoluis]

That's true.
In my case works nice, because my trigger functions just receive table names or column names, but in your case, it will not work.
You can then just split the string by the comma (,) and trim lead and back whitespaces. But be careful not to split with comma inside strings. Then you'll have to check for quotes.

[decibel]

Here's what I'm thinking, though I haven't added trigger__get_oids yet: #3

[lizardoluis]

If you're trying to find what trigger on a particular table uses a
particular trigger function, I think it would be better to have a
function that searches for that; something like

FUNCTION

cat_tools.trigger__get_oids(
trigger_table regclass
, trigger_function regproc
) RETURNS SETOF oid

You could then do

SELECT trigger__parse(oid) FROM trigger__get_oids(...) oid

Your function trigger__parse, with the modifications I did, was already enough. It solved all my problems.
Thanks a lot.

[decibel]

I've submitted changes to master that should handle everything you wanted here. Please check them ASAP and let me know if they make sense.