update_pg_pwd and AR triggers - Mailing list pgsql-hackers

From wieck@debis.com (Jan Wieck)
Subject update_pg_pwd and AR triggers
Date
Msg-id m120Xoi-0003kHC@orion.SAPserv.Hamburg.dsh.de
Whole thread Raw
List pgsql-hackers
Hi,

    I   have   additional   information  on  the  update_pg_pwd()
    discussion,  whether  AFTER  ROW   triggers   should   return
    HeapTuple  or  void.   The return value of AFTER ROW triggers
    isn't void - definitely.

    The trigger manager tries to pfree() the returned pointer, if
    it's  neither NULL, nor one of the tuples he sent down to the
    trigger (trigtuple and newtuple).

    Thus, ANY trigger must at least return (HeapTuple)NULL.

    Fix is committed.


Jan

--

#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#========================================= wieck@debis.com (Jan Wieck) #

pgsql-hackers by date:

Previous
From: Keith Parks
Date:
Subject: RE: [HACKERS] NOTICE: LockRelease: locktable lookup failed, no lock
Next
From: "neil d. quiogue"
Date:
Subject: Re: [HACKERS] Re: QUESTION: Replication