X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D3AFE9DC9A7 for ; Sun, 26 Mar 2006 20:07:10 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 12962-02 for ; Sun, 26 Mar 2006 20:07:13 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from zproxy.gmail.com (zproxy.gmail.com [64.233.162.193]) by postgresql.org (Postfix) with ESMTP id 5D5279DC960 for ; Sun, 26 Mar 2006 20:07:08 -0400 (AST) Received: by zproxy.gmail.com with SMTP id v1so1353935nzb for ; Sun, 26 Mar 2006 16:07:11 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=eoLJY3BhvKXVQqNW02kfp9wzH+ZkOOKKdtxsimbmte9NhTjkTS4qB2R6Zow/wtoiqkrGDGLu5NNSOWt2Byp8zqRUO7t6+rmHVYJibXU4wN9YE9kORNm+qyyt0pXhKVOekEd+Dy03omWzH4/Bqtz6HySQd1+Ooqatg3N7Vxkv/Pc= Received: by 10.65.239.5 with SMTP id q5mr1089354qbr; Sun, 26 Mar 2006 16:07:11 -0800 (PST) Received: by 10.65.53.2 with HTTP; Sun, 26 Mar 2006 16:07:11 -0800 (PST) Message-ID: <1c66bda80603261607k97a7502o99c5402979452859@mail.gmail.com> Date: Mon, 27 Mar 2006 12:07:11 +1200 From: adey To: Pgsql-Admin Subject: Fwd: Notice Processor hook In-Reply-To: <1c66bda80603131251v49a6ca6y5a0421f4395f9d5d@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4148_19321322.1143418031570" References: <1c66bda80603131251v49a6ca6y5a0421f4395f9d5d@mail.gmail.com> X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.536 required=5 tests=[AWL=0.259, HTML_MESSAGE=0.001, MAILTO_TO_SPAM_ADDR=0.276] X-Spam-Score: 0.536 X-Spam-Level: X-Archive-Number: 200603/280 X-Sequence-Number: 21037 ------=_Part_4148_19321322.1143418031570 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Below is an old message from Tom Lane regarding "Notice Processor hook". I have not been able to contact him to explain it, nor does it appear in the Postgresql.org archives. Would one of you be able to help me to implement this please? We are trying to obtain the output from a vacuum run by automated script. ---------- Forwarded message ---------- From: adey Date: Mar 14, 2006 8:51 AM Subject: Notice Processor hook To: Tom Lane Hi Tom, A colleague found this entry from yourself in thescripts.com:- "Adam H.Pendleton" writes:[color=3Dblue] > When running a "VACUUM VERBOSE" query using PQsendQuery, > PQconsumeInput, and PQisBusy, all the "INFO:" output from the "VACUUM > VERBOSE" command is printed on the terminal, and is not available > through the PGresult structure.[/color] You could capture that output by setting up a notice processor hook routine. regards, tom lane We are having similar problems - please could you tell me how to implement = a "Notice Processor hook"? Adrian ------=_Part_4148_19321322.1143418031570 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Below is an old message from Tom Lane regarding "Notice Processor hook= ". I have not been able to contact him to explain it, nor does it appe= ar in the Postgresql.org archives. Wo= uld one of you be able to help me to implement this please? We are trying t= o obtain the output from a vacuum run by automated script.

---------- Forwarded message ----------
From: adey <adey11@gmail.com>
Date: Mar 14, 2006 8:51 AM
Sub= ject: Notice Processor hook
To: Tom Lane <tgl@sss.pgh.pa.us= >

Hi Tom,
A colleague found this entry from yourself in thescripts.com:-
 
"Adam H.Pendleton" <fmonkey@fmonkey.net> writes:[color=3Dblue]
> When running a = "VACUUM VERBOSE" query using PQsendQuery,
> PQconsumeInput, and PQisBusy, all the "INFO:" output fro= m the "VACUUM
> VERBOSE" command is printed on the termina= l, and is not available
> through the PGresult structure.[/color]

You could capture that output by setting up a notice processor hook=
routine.

regards, tom lane
 
 
We are having similar problems - please could you tell me how to imple= ment a "Notice Processor hook"?
 
Adrian
------=_Part_4148_19321322.1143418031570--