nies.david wrote:

Debug output ($wgDebugLogfile)

Attached:

nies.david wrote:

I added the whole debug output ($wgDebugLogFile) in the attached file "Debug output ($wgDebugLogfile)"

overlordq wrote:

When I ran the query I had problems with the following special pages:

Uncategorizedcategories
Uncategorizedpages
Uncategorizedimages
Uncategorizedtemplates
Unusedimages

Withoutinterwiki

This is likely due to my test wiki being relatively empty.

For the first one, Uncategorizedcategories, you get the following query:

SELECT

        'Uncategorizedcategories' as type,
        page_namespace AS namespace,
        page_title AS title,
        page_title AS value
FROM page
LEFT JOIN categorylinks ON page_id=cl_from
WHERE cl_from IS NULL AND page_namespace=14 AND page_is_redirect=0
 ORDER BY value  LIMIT 1000  OFFSET 0

The problem is the page_title AS value. In the ::recache function of QueryPage.php it uses the value field as an insert into the querycache.

INSERT /* UncategorizedCategoriesPage::recache */ INTO querycache (qc_type,qc_namespace,qc_title,qc_value) VALUES ('Uncategorizedcategories','14','Rainbow_Tables','Rainbow_Tables')

Looking at tables.sql, qc_value should be an unsigned integer but the getSQL() function of SpecialUncategorizedpages.php is feeding it the page_title as seen above. Just a hazarding a guess but this is likely the cause for the other errors as well.

This however should effect MySQL as well, so either MySQL is silently accepting a text field as an integer or MySQL is doing something else weird.

overlordq wrote:

for the hellofit on MySQL:

mysql> SELECT * FROM querycache;
Empty set (0.01 sec)

mysql> INSERT INTO querycache (qc_type,qc_namespace,qc_title,qc_value) VALUES ('Uncategorizedcategories','14','Rainbow_Tables','Rainbow_Tables');
Query OK, 1 row affected, 1 warning (0.00 sec)

mysql> SELECT * FROM querycache;
+-------------------------+----------+--------------+----------------+

+-------------------------+----------+--------------+----------------+

+-------------------------+----------+--------------+----------------+
1 row in set (0.01 sec)

So at least in MySQL's (non-strict) behavior it'll silently accept this invalid input and substitute a zero.

But enabling strict mode will throw an error:

mysql> SET SESSION sql_mode=STRICT_ALL_TABLES;
Query OK, 0 rows affected (0.00 sec)

mysql> INSERT INTO querycache (qc_type,qc_namespace,qc_title,qc_value) VALUES ('Uncategorizedcategories','14','Rainbow_Tables','Rainbow_Tables');

ERROR 1366 (HY000): Incorrect integer value: 'Rainbow_Tables' for column 'qc_value' at row 1

So, renaming the bug since it isn't limited to PG, it's just PG by default throws an error.

fixed in r47622.

Migrating from the old tracking task to a tag for PostgreSQL-related tasks.