From: | Kevin Grittner <kgrittn(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | ProPAAS DBA <dba(at)propaas(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: raise notice question |
Date: | 2017-01-16 20:32:52 |
Message-ID: | CACjxUsMD+B-+-K-wSMs=CCvxt6cCgY_1XvqhUOEh3QBaSmi02w@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Sat, Jan 14, 2017 at 11:15 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> ProPAAS DBA <dba(at)propaas(dot)com> writes:
>> Is it possible to execute a raise notice without the "Notice" keyword
>> being part of the output
> This is a matter for how your client code presents the message data.
> So far as psql is concerned, the answer would be "no", but a custom
> application could deconstruct the notice message however it wanted.
It wouldn't be crazy to provide a way in psql to suppress the level only
for NOTICE. It would become much more important to be able to do so
(and perhaps do so by default) if we get stored procedures which can
return a complex result stream like TDS does. The series of literals
and results sets of different types is something which can be quite
useful to DBAs.
--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Patrick B | 2017-01-16 21:15:31 | Custom type column index - Postgres 9.1 |
Previous Message | Kevin Grittner | 2017-01-16 20:00:04 | Re: Re: Are new connection/security features in order, given connection pooling? |