From: | "Plugge, Joe R(dot)" <JRPlugge(at)west(dot)com> |
---|---|
To: | Marc Fromm <Marc(dot)Fromm(at)wwu(dot)edu>, "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: postgresql logs |
Date: | 2010-09-22 17:27:24 |
Message-ID: | BD69807DAE0CE44CA00A8338D0FDD08302E5F85B63@oma00cexmbx03.corp.westworlds.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
What platform is this running on? It looks as if someone executed a sql script from the Windows environment that contains the control characters and pointed it to postgres running on Linux/Unix.
From: pgsql-admin-owner(at)postgresql(dot)org [mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Marc Fromm
Sent: Wednesday, September 22, 2010 12:19 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: [ADMIN] postgresql logs
In my postgresql logs, found in the pg_log folder, there are several sql syntax errors where the sql statement is broken up with the characters "^M". The error is at the first field name that is broken up by the ^M as shown below in the example. The ^M breaks up the field reference2zip by splitting it into "r^M" and "eference2zip".
Example
-ERROR: syntax error at or near "eference2zip" at character 699
INSERT INTO loan_requests (loantype,loan_amt,studentfname,studentlname,studentid,studentdlicense,studentemail,curstudentstreet,curstudentcity,curstudentstate,curstudentzip,curstudentcountry,curstudentphone,permstudentstreet,permstudentcity,permstudentstate,permstudentzip,permstudentcountry,permstudentphone,employername,employerstreet,employercity,employerstate,employerzip,employercountry,parentfname,parentlname,parentstreet,parentcity,parentstate,parentzip,parentcountry,parentphone,reference1fname,reference1lname,reference1street,reference1city,reference1state,reference1zip,reference1country,reference1phone,reference2fname,reference2lname,reference2street,reference2city,reference2state,r^M
eference2zip,reference2country,reference2phone,explanation,reason,status) VALUES ('zzz','zzz','zzz','zzz','zzz','zzz','zzz^M
zzz', . . . )
Any ideas on what is generating the ^M and breaking up the sql statement so that it cannot be executed?
Marc
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Rostron | 2010-09-22 22:18:02 | long-running autovacuum tasks |
Previous Message | Marc Fromm | 2010-09-22 17:18:49 | postgresql logs |