Re: [PATCH] SQL function to report log message

From: Jim Nasby <Jim(dot)Nasby(at)BlueTreble(dot)com>
To: dinesh kumar <dineshkumar02(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net>
Cc: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <david(at)fetter(dot)org>, Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCH] SQL function to report log message
Date: 2015-11-17 07:16:40
Message-ID: 564AD458.1050001@BlueTreble.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 11/15/15 10:56 PM, dinesh kumar wrote:
> So, shall we make this pg_report_log TO pg_write_log OR pg_ereport OR
> <SOME OTHER GOOD SUGGESTIONS> from you.

Why not pg_raise to mirror plpgsql? (The function does have the same
semantics, right? It's not doing something like only sending to the log
and not the client?)
--
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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message dinesh kumar 2015-11-17 07:19:38 Re: Proposing COPY .. WITH PERMISSIVE
Previous Message Jim Nasby 2015-11-17 07:13:53 Re: Proposal: "Causal reads" mode for load balancing reads without stale data