Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id 3FFA964FD9F for ; Tue, 18 Nov 2008 07:10:17 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 41673-03 for ; Tue, 18 Nov 2008 07:10:13 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by mail.postgresql.org (Postfix) with ESMTP id DCF7164FD38 for ; Tue, 18 Nov 2008 07:10:13 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.14.1/8.14.1) with ESMTP id mAIBA9a7034846 for ; Tue, 18 Nov 2008 07:10:09 -0400 (AST) (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.14.1/8.14.1/Submit) id mAIAejhP005750 for pgsql-admin@postgresql.org; Tue, 18 Nov 2008 06:40:45 -0400 (AST) (envelope-from news) From: "Sabin Coanda" X-Newsgroups: pgsql.admin Subject: raise doesn't add end of line Date: Tue, 18 Nov 2008 12:40:13 +0200 Organization: Hub.Org Networking Services Lines: 49 Message-ID: X-Complaints-To: usenet@news.hub.org X-Priority: 3 X-MSMail-Priority: Normal X-Newsreader: Microsoft Outlook Express 6.00.2900.5512 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.5512 X-RFC2646: Format=Flowed; Original To: pgsql-admin@postgresql.org X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200811/94 X-Sequence-Number: 30748 Hi there, I upgrade "PostgreSQL 8.2.4 on i686-pc-mingw32, compiled by GCC gcc.exe (GCC) 3.4.2 (mingw-special)" to "PostgreSQL 8.3.5, compiled by Visual C++ build 1400". I found running a function which logs many logs has different behavior in command line comparing with the query window output pane of pgAdmin. I found that many RAISE statements in a function no more adds end of line (CR/LF) on every message, even if it contains chr(10) explicitely. Just when the function ends, or inserting chr(10) in the middle of the message a CR/LF is added in the log. For instance consider the function: CREATE OR REPLACE FUNCTION r() RETURNS void AS $BODY$begin raise notice 'Break the 1st%line...', chr(10); raise notice 'eol on 2nd line...%', chr(10); raise notice '3rd line'; raise notice '4th line'; end; $BODY$ LANGUAGE 'plpgsql' VOLATILE COST 100; ALTER FUNCTION r() OWNER TO postgres; Run it: SELECT r() On windows command prompt you get a right log: NOTICE: Break the 1st line... NOTICE: eol on 2nd line... NOTICE: 3rd line NOTICE: 4th line But on pgAdmin output pane, you get a wrong log: NOTICE: Break the 1st line...NOTICE: eol on 2nd line...NOTICE: 3rd lineNOTICE: 4th line Sabin