This is Drupal 7 alpha1 with PostgreSQL 8.3.

When Detailed Logging is enabled, the following error occurs in each page: SQLSTATE[22P02]: Invalid text representation: 7 ERROR: invalid input syntax for integer: "171.730000" (of course, the number changes with every page).

When Summary logging (DB) is enabled, the following error occurs in each page: Fatal error: Exception thrown without a stack frame in Unknown on line 0. I guess this is due to PostgreSQL too.

Comments

kbahey’s picture

kbahey CreditAttribution: kbahey commented
Status: Active » Postponed (maintainer needs more info)

Looks like something is defined as an integer while a float is being used for that column. Need to know which column it is. Do you have the query text for the first error?

I have no idea what the second error is.

ogi’s picture

ogi CreditAttribution: ogi commented

The query is INSERT INTO performance_detail (timestamp, bytes, ms, query_count, query_timer, anon, path, data) VALUES ($1, $2, $3, $4, $5, $6, $7, $8) and it looks like the problem is with ms because the values are always very close to what devel shows at the bottom of the page.

kbahey’s picture

kbahey CreditAttribution: kbahey commented
Version: 7.x-1.0-alpha1 » 7.x-1.x-dev
Status: Postponed (maintainer needs more info) » Fixed

I committed a fix that will be in the 7.x-1.x-dev in about 4 hours from now.

The fix is to cast values as int, since microseconds are not very relevant here.

Try it and let me know if it does not work.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

ogi’s picture

ogi CreditAttribution: ogi commented
Status: Closed (fixed) » Active

http://drupalcode.org/project/devel.git/blobdiff/2d3443846bc19910df4dab6... fixes only one use case. In the same function there's code that doesn't have casting to int.

salvis’s picture

salvis
he/his
CreditAttribution: salvis commented
Status: Active » Closed (won't fix)

The Performance submodule has been removed from Devel for lack of resources to maintain it properly.

We hope it will come back in its original project, http://drupal.org/project/performance / Performance Logging and Monitoring, which is currently marked "Abandoned." If you're interested in maintaining this important project then see Dealing with abandoned projects.

Unfortunately, the issues queue of Performance has been closed and I cannot reassign this issue, so I just have to close it.