artifact_id;status_id;status_name;priority;submitter_id;submitter_name;assigned_to_id;assigned_to_name;open_date;close_date;last_modified_date;summary;details;"Category";"Group";"Resolution" 1000795;1;"Open";3;1872;"Michal Taborsky";101537;"Guillaume Smet";"2006-12-02 12:48";"";"2012-09-24 02:14";"Missing method QueryLogObject::appendDetail()";"I am using 0.7.1 installed from RPM on CentOS 4.4 (Redhat ES 4). I am getting this error. Indeed, the method does not exists. PHP Fatal error: Call to undefined method QueryLogObject::appendDetail() in /usr/share/pgfouine/include/postgresql/lines/PostgreSQLDetailLine.class.php on line 28 The callign code is: class PostgreSQLDetailLine extends PostgreSQLLogLine { var $ignore = false; function appendTo(& $logObject) { $logObject->appendDetail($this->text); } } ";"None";"None";"None" 1010210;1;"Open";3;107725;"Dmitry Koterov";101537;"Guillaume Smet";"2007-12-05 21:47";"";"2012-09-24 02:14";"Two bugs with parsing ""HINT:"" and ""free space"" lines";"Hello. I have to pre-filter by Postgres logs with grep -v ""HINT:\|free space"" because else I've got PHP errors: 1. For pgfouine: PHP Fatal error: Call to undefined method QueryLogObject::appendHint() in /usr/share/pgfouine/include/postgresql/lines/PostgreSQLHintLine.class.php on line 28 2. For pgfouine_vacuum: PHP Fatal error: Call to undefined method FSMInformationLogObject::addIndexInformation() in /usr/share/pgfouine/include/postgresql/vacuum/lines/PostgreSQLIndexCleanupInformationLine.class.php on line 39 Seems somewhere in the code (I have spent about 20 minutes to learn it, but failed with it) logger passed to appendTo() is not proper.";"None";"None";"None" 1010445;1;"Open";3;110091;"Michael Ronin";100;"Nobody";"2008-08-01 21:50";"";"2012-09-24 02:14";"Pgfouine error";" PHP Fatal error: Call to undefined method PreparedStatementLogObject::appendHint() in /home/pgfouine/pgfouine-1.0/pgfouine-1.0/include/postgresql/lines/PostgreSQLHintLine.class.php on line 28 ";"None";"None";"None" 1010589;1;"Open";3;114334;"Dmitri Koulikov";100;"Nobody";"2009-04-02 13:52";"";"2012-09-24 02:14";"PHP Fatal errors: undefined method and memory exhausted";"there are two logs attached one for the error: PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 5355 bytes) in /home/dima/devel/linkfeed/pg_logs/pgfouine-1.0/include/listeners/query/NormalizedQueriesListener.class.php on line 81 and the other for PHP Fatal error: Call to undefined method QueryLogObject::appendHint() in /home/dima/devel/linkfeed/pg_logs/pgfouine-1.0/include/postgresql/lines/PostgreSQLHintLine.class.php on line 28 It seems some scrip memory is overwritten by the data";"None";"None";"None" 1010614;1;"Open";3;100263;"Russell Smith";101537;"Guillaume Smet";"2009-04-30 04:54";"";"2012-09-24 02:14";"HINT: anywhere in the line produces a parse failure";"1000795 Missing method QueryLogObject::appendDetail() 1010210 Two bugs with parsing ""HINT:"" and ""free space"" lines 1010445 Pgfouine error All appear to have the same base bug. The logline parser is finding a keyword in the wrong location on the line. The following is my example of how to produce this. PHP Fatal error: Call to undefined method QueryLogObject::appendHint() in /web/htdocs/bsusas/pgfouine-1.1/include/postgresql/lines/PostgreSQLHintLine.class.php on line 28 Error. This is with the latest 1.1, just downloaded. Logfile is attached as break.log ";"None";"None";"None" 1010619;1;"Open";3;114988;"Srinivas Bethi";100;"Nobody";"2009-05-07 00:04";"";"2012-09-24 02:14";"pg_fouine 1.1 reporting incorrect time in analysis report";" pg_fouine 1.1 reporting incorrect time in analysis report. This working correctly in 1.0. V 1.1 shows 14.09s for this stmt. It actually took 985.5 secs. create temp table property_score_part_new as select p.property_id, 5301 as score_part_id, case count(distinct (pm.media_id)) when 0 then 0 else case when count(distinct (pm.media_id)) between 1 and 3 then 30 when count(distinct (pm.media_id)) between 4 and 6 then 45 when count(distinct (pm.media_id)) between 7 and 10 then 55 when count(distinct (pm.media_id)) > 10 then 60 else 0 end + case when count(distinct (f.floorplan_id))::decimal > 0 then (25 * count (distinct (f.image_media_id))/count(distinct (f.floorplan_id))::decimal)::integer else 0 end + case when count(distinct (fm.floorplan_id)) >= count(distinct (f.floorplan_id)) then 15 else 0 end end + case count(pv.video_id) when 0 then 0 else 50 end as new_value from property p left join property_media pm using (property_id) left join floorplan f on f.property_id = p.property_id and f.is_active and f.is_displayed left join floorplan_media fm using (floorplan_id) left join property_video pv on pv.property_id = p.property_id and pv.is_displayed group by 1,2 union all select p.property_id, 5304, case sign (50 - 2*(current_date - (max(rent_modified_timestamp))::date)/7) when 1 then case sign (10 - 2*(max(rent_modified_timestamp)::date - min(rent_modified_timestamp)::date)/7) when 1 then 10 - 2*(max(rent_modified_timestamp)::date - min(rent_modified_timestamp)::date)/7 else 0 end + 50 - 2*(current_date - (max(rent_modified_timestamp))::date)/7 else 0 end + 25 from property p left join floorplan f on f.property_id = p.property_id and f.is_active and f.is_displayed group by 1,2 union all select property_id, 5307, case listing_level_id when 23 then 75 when 21 then 0 else -75 end from property ;";"None";"None";"None" 1010769;1;"Open";3;127839;"Sébastien Koechlin";100;"Nobody";"2010-02-26 16:36";"";"2012-09-24 02:14";"PHP Warning: date(): It is not safe to rely on the system's timezone settings.";"I have gigabytes of warning when using pgfouine-1.2-1. Here is an example avec a single line: $ cat pgsql Feb 19 11:53:14 localhost postgres[27417]: [68-1] LOG: statement: select Utilisateurs.* from Utilisateurs WHERE Utilisateurs.login = 'xx' $ pgfouine.php -file pgsql > /dev/null PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/share/pgfouine/include/postgresql/parsers/SyslogPostgreSQLParser.class.php on line 78 PHP Warning: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/share/pgfouine/include/postgresql/parsers/SyslogPostgreSQLParser.class.php on line 78 PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/share/pgfouine/include/reporting/HtmlReportAggregator.class.php on line 120 PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/share/pgfouine/include/lib/common.lib.php on line 79 PHP Warning: date(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'Europe/Berlin' for 'CET/1.0/no DST' instead in /usr/share/pgfouine/include/lib/common.lib.php on line 79 $ locale LANG=fr_FR.UTF-8 LC_CTYPE=""fr_FR.UTF-8"" LC_NUMERIC=""fr_FR.UTF-8"" LC_TIME=""fr_FR.UTF-8"" LC_COLLATE=""fr_FR.UTF-8"" LC_MONETARY=""fr_FR.UTF-8"" LC_MESSAGES=""fr_FR.UTF-8"" LC_PAPER=""fr_FR.UTF-8"" LC_NAME=""fr_FR.UTF-8"" LC_ADDRESS=""fr_FR.UTF-8"" LC_TELEPHONE=""fr_FR.UTF-8"" LC_MEASUREMENT=""fr_FR.UTF-8"" LC_IDENTIFICATION=""fr_FR.UTF-8"" LC_ALL= $ lsb_release -a LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch Distributor ID: CentOS Description: CentOS release 5.4 (Final) Release: 5.4 Codename: Final $ rpm -qa | grep php php-mysql-5.3.1-1.el5.remi php-cli-5.3.1-1.el5.remi php-mcrypt-5.3.1-1.el5.remi php-common-5.3.1-1.el5.remi php-5.3.1-1.el5.remi php-mbstring-5.3.1-1.el5.remi php-pdo-5.3.1-1.el5.remi php-gd-5.3.1-1.el5.remi $ rpm -q pgfouine pgfouine-1.2-1 ";"None";"None";"None" 1010770;1;"Open";3;127839;"Sébastien Koechlin";100;"Nobody";"2010-02-26 18:10";"";"2012-09-24 02:14";"Invalid results displayed when using 'ms' durationunit";"Using pgfouine-1.2-1 -format html-with-graphs -durationunit ms I have odd results, unit is wrong: Slowest queries (N) =================== Rank: 1 Av. duration (ms): 1,013.61 Times executed: 2 Total duration: 2,027.2s Rank: 2 Av. duration (ms): 1,013.25 Times executed: 2 Total duration: 2,026.5s Two queries running for about 1 second (1013ms) can not have a total duration of 2000sec (around 34 min) Queries that took up the most time (N) ====================================== Rank: 37 Total duration: 2,027.2s Times executed: 2 Av. duration (ms): 1,013.61 Rank: 38 Total duration: 2,026.5s Times executed: 2 Av. duration (ms): 1,013.25 Most frequent queries (N) ========================= Rank: 43 Times executed: 819 Total duration: 432.1s Av. duration (ms): 0.53 ";"None";"None";"None" 1010901;1;"Open";3;173601;"Mladen Gogala";100;"Nobody";"2010-09-22 21:37";"";"2012-09-24 02:14";"auto_explain module confuses PgFouine";"When I load auto_explain module, PgFouine thinks that the plan is actually a SQL statement. The problematic report is attached.";"None";"None";"None" 1010943;1;"Open";3;189170;"Mark Mikulec";100;"Nobody";"2010-11-10 18:51";"";"2012-09-24 02:14";"Call to undefined method DurationLogObject::appendContext()";"Call to undefined method DurationLogObject::appendContext() in /usr/share/pgfouine-1.2/include/postgresql/lin es/PostgreSQLContextLine.class.php on line 50 This happens 200,000+ lines into a very large log file filled with unreleasable database schemas. I'm not sure what else I can do by saying the log is filtered for only 1000ms+ queries, and that it's Postgres 8.3.7. I have tried both version 1.0 and the latest one that I manually downloaded from the site. Thank you.";"None";"None";"None" 1011137;1;"Open";3;107391;"Laurenz Albe";100;"Nobody";"2011-12-20 14:02";"";"2012-09-24 02:14";"csvlog support broken for PostgreSQL >= 9.0";"In PostgreSQL 9.0, the format for csvlog log files changed: a new column ""application_name"" was appended. This makes pgFouine gag with the following message: pgFouine did not find any valid PostgreSQL log line in your log file: * check that PostgreSQL uses an english locale for logging (lc_messages in your postgresql.conf), * check that you use the -logtype option (syslog, stderr) according to your log file, * if you use syslog and log_line_prefix, check that your log_line_prefix has a trailing space, * if you use stderr, check that your log_line_prefix is of the form '%t [%p]: [%l-1] '. If you think your log file and your options are correct, please contact the author (gsmet on #postgresql@freenode or guillaume-pg at smet dot org).";"None";"None";"None" 1011169;1;"Open";3;444892;"Aart de Vries";100;"Nobody";"2012-02-28 20:50";"";"2012-09-24 02:14";" Undefined index: 100000000 SlowestQueryList.class.php on line 5";"I get the following error: Undefined index: 100000000 in /home/random/srcdir/pgfouine-1.2/include/SlowestQueryList.class.php on line 52 This results from using an uninitialized variable at the indicated position. Please fix this. ";"None";"None";"None"