SPI question re elog() and aborted transactions?

I have a C trigger function using SPI.  It's purpose is never more important
than the transaction itself, so I don't ever want the C function to abort
the transaction under any circumstances.

Can I accomplish this by simply never calling elog(ERROR, ...)?  (And not
crashing or doing anything else programmatically mischievous, of course).

Ed