https://bugzilla.wikimedia.org/show_bug.cgi?id=24629

           Summary: Eliminating noise from postgres logs
           Product: MediaWiki
           Version: 1.15.5
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: enhancement
          Priority: Normal
         Component: Database
        AssignedTo: wikibugs-l@lists.wikimedia.org
        ReportedBy: to...@gildseth.com


Created an attachment (id=7610)
 --> (https://bugzilla.wikimedia.org/attachment.cgi?id=7610)
10 lines changed/added in includes/db/DatabasePostgres.php

We are running a number of instances of mediawiki on PostgreSQL and are getting
a large amount of warning messages in the postgres log, which could easily be
fixed with a few simple changes to DatabasePostgres.php. The messages in
question are the following:


Message about escape string syntax:
=========================================
[2010-07-01 00:02:30.022 CEST] [dbpg-bloggwiki] [mediawiki:mediawiki] WARNING:
nonstandard use of \\ in a string literal at character 25
[2010-07-01 00:02:30.022 CEST] [dbpg-bloggwiki] [mediawiki:mediawiki] HINT: 
Use the escape string syntax for backslashes, e.g., E'\\'.
=========================================


And warning message when calling "COMMIT" when no transaction is in progress
=========================================
[2010-07-01 00:10:08.521 CEST] [dbpg-bloggwiki] [mediawiki:mediawiki] WARNING: 
there is no transaction in progress
=========================================


It's not that it's a critical problem, but it would be nice to avoid filling up
our logs with 1-2GB of these kind of messages per month, in addition to it
being more correct.

-- 
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.

_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l

Reply via email to