On Tue, April 7, 2009 16:07, Tom Lane wrote:
>
> You might find it more useful to add some elog(LOG) statements to
> the trigger body.
>
Thank you again. I will go through section 44.2 tonight.
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrnemailto:b
"James B. Byrne" writes:
> I am poking in the dark here. What I want to do is to determine if
> the trigger is firing and whether the function works as intended.
> At the moment I am not seeing anything show up in the secondary
> table so I have done something wrong. Is there some way of gettin
On Tue, April 7, 2009 15:09, Tom Lane wrote:
>
> ALTER DATABASE foo SET log_min_messages = whatever;
>
> Note this will only affect subsequently-started sessions. Also,
> if memory serves, you have to be superuser to set this particular
> variable.
Thanks. Am I correct to infer from the output
"James B. Byrne" writes:
> I am testing the trigger function that I wrote. Is there a way to
> increase the logging detail level for just a single database
> instance?
ALTER DATABASE foo SET log_min_messages = whatever;
Note this will only affect subsequently-started sessions. Also,
if memory
AL] INSERT or UPDATE TRIGGER
I am testing the trigger function that I wrote. Is there a way to
increase the logging detail level for just a single database
instance? The manual indicates not, but just in case I am
misreading things I am asking here?
--
*** E-Mail is NOT a SECU
I am testing the trigger function that I wrote. Is there a way to
increase the logging detail level for just a single database
instance? The manual indicates not, but just in case I am
misreading things I am asking here?
--
*** E-Mail is NOT a SECURE channel ***
James B. Byrn
This is what I have come up with. Comments are welcomed.
CREATE OR REPLACE FUNCTION hll_pg_fn_ident_insert()
RETURNS TRIGGER AS $pg_fn$
-- ROW AFTER TRIGGER
-- trigger passes identifier_type, _value and _description
-- received as ARGV[0], ARGV[1] and ARGV[2]
