2. Using this function, if we provide any "NULL" argument to the function, we should either skip it or report it. I see this is what the function is doing.
postgres=# SELECT pg_report_log('INFO', 'NULL', false, 'NULL', 'NULL'); INFO: NULL DETAIL: NULL /-- Are you suggesting to change this behaviour/ HINT: NULL
It should operate the same as what was decided for RAISE.
I am sorry, there was more opinions - what was decided for RAISE?
I'd say it should also support the remaining RAISE options as well (COLUMN, CONSTRAINT, DATATYPE, TABLE, SCHEMA).
I think hide_statement is a better name than ishidestmt. It would be nice if RAISE supported that too...
I think the function should also allow specifying a condition name instead of a SQL state, same as RAISE does.
In other words, this function and raise should operate exactly the same unless there's a really strong reason not to. Otherwise it's just going to create confusion.
I have different opinion - if RAISE and this function is exactly same,then the function has not sense. There should not be principal difference, but in same behave I don't see any sense.
-- Jim Nasby, Data Architect, Blue Treble Consulting, Austin TX Experts in Analytics, Data Architecture and PostgreSQL Data in Trouble? Get it in Treble! http://BlueTreble.com
