Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by hub.org (8.10.1/8.11.0) with ESMTP id e9R5bfq02775 for ; Fri, 27 Oct 2000 01:37:42 -0400 (EDT) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id e9R5Xf528252; Fri, 27 Oct 2000 01:33:41 -0400 (EDT) To: Sandis Jerics cc: pgsql-sql@postgresql.org Subject: Re: HELP! ... pg_locale ??? In-reply-to: <10741.001026@parks.lv> References: <39F78FE7.DA915769@agliodbs.com> <10741.001026@parks.lv> Comments: In-reply-to Sandis Jerics message dated "Thu, 26 Oct 2000 17:48:26 +0300" Date: Fri, 27 Oct 2000 01:33:41 -0400 Message-ID: <28249.972624821@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200010/255 X-Sequence-Number: 1923 Sandis Jerics writes: > As result, now all queries, written inside the php code on multiply lines, > returns the following: > ERROR: parser: parse error at or near " " At a guess, you're having trouble with newline representations (Unix convention is \n only, DOS/Windows convention is \r\n, and then there's Macintosh which likes \r only). We've been working to change Postgres to accept all of these choices, but depending on which version of which tool you are using, you may need to toe the Unix line faithfully. The above message looks a lot like something spitting up on a stray \r. Dunno what your admin did to make the problem appear where you hadn't had it before... regards, tom lane