All work
- xtrabackup --move-back produces malformed binlog.index entryPXB-3496
- xbcloud cause Segmentation fault with tls1.2PXB-3493
- Xtrabackup continues the prepare after reach error on xtrabackup_apply_deltaPXB-3492
- Why don't xtrabackup8 acquire locks when --no-backup-locks=1PXB-3491Resolved issue: PXB-3491
- Invalid URL for Boost tarball in Xtrabackup 8.0.35-32PXB-3490Satya Bodapati
- test for dashboardPXB-3488
- Long Running xbcloud AWS Backups FailPXB-3486
- Produce Accessibility Conformance Report for Percona XtraBackupPXB-3479
- xbstream does long post-processing after receiving all dataPXB-3470Satya Bodapati
- Optimize deleted files handling with reduced lockPXB-3468
- Missing 'posix_fadvise(file, 0, 0, POSIX_FADV_SEQUENTIAL)' when reading the redo log filesPXB-3467Resolved issue: PXB-3467Satya Bodapati
- test for attachementsPXB-3466Resolved issue: PXB-3466
- --defaults-file is ignored by xtrabackup in --prepare modePXB-3465
- Bash process substitution for --defaults-file and --defaults-extra-file args doesn't work anymorePXB-3464
- Wrong default value of innodb_flush_methodPXB-3463
- Allow supplying the MySQL password in an environment variablePXB-3462
- Remove version check from PXB 8.4PXB-3461Satya Bodapati
- Backup fails with Vault related errorPXB-3460
- Xtrabackup failing to take backup on Mysql server where keyring is enabledPXB-3459
- Parameterize "PERCONA_SCHEMA.xtrabackup_history"PXB-3455
- [DOCS] - add an index 8.0PXB-3454Resolved issue: PXB-3454patrick.birch
- SST timeouts when mysqld takes more than 5 minutes to startPXB-3434
- Restore fails if non-defaults variables are usedPXB-3458
- Xtrabackup can not backup replicaPXB-3433Aaditya Dubey
- Assertion failure: log0recv.cc:4340:log.m_files.find(recovered_lsn) != log.m_files.end()PXB-3431
- Error when using Smart memory.PXB-3430Aaditya Dubey
- Error when using Smart memory.PXB-3429Resolved issue: PXB-3429
- Parallelize incremental delta apply in incremental backup preparePXB-3427Resolved issue: PXB-3427Satya Bodapati
- Using KMIP component causes double free of memory on error pathsPXB-3426Resolved issue: PXB-3426Satya Bodapati
- When running XtraBackup on unsupported MySQL 9 version, it shows a message to use 9.1 version that doesn't existsPXB-3423
- xtrabackup got signal if --databases= very longPXB-3421
- xtrabackup got signal 11PXB-3420Resolved issue: PXB-3420
- xtrabackup fails with 'got signal 6' errorPXB-3412Resolved issue: PXB-3412
- Benchmark the performance of reduced lock featurePXB-3411Resolved issue: PXB-3411Satya Bodapati
- PXB 84 Creating Backup on replica failsPXB-3399Resolved issue: PXB-3399Satya Bodapati
- Merge mysql-9.1.0PXB-3396Resolved issue: PXB-3396aibek.bukabayev
- Verify latest version of PXB works with the newly created PS versionPXB-3395Resolved issue: PXB-3395mohit.joshi
- Verify PXB 8.0.35 works with PS 8.0.40PXB-3394Resolved issue: PXB-3394mohit.joshi
- General tablespaces are not handled properly when located in external data directoryPXB-3393Resolved issue: PXB-3393aibek.bukabayev
- xtrabackup doesn't pick up --innodb-log-group-home-dir config parameterPXB-3392
- Release PXB 8.0.35-32 (Q2 2024)PXB-3384Resolved issue: PXB-3384aibek.bukabayev
- Allow Xbcloud to respect AWS_CONFIG_FILE and AWS_PROFILE env variable configured using AWS RolesAnywherePXB-3382
- Implement check to fail early if number of open file handles is not same as number of files in datadirPXB-3381Resolved issue: PXB-3381Satya Bodapati
- Test new approach to handle duplicate filesPXB-3378Resolved issue: PXB-3378aibek.bukabayev
- Slave (replica) backup fails (8.4)PXB-3377Resolved issue: PXB-3377
- fut0lst.ic:82:addr.page == FIL_NULL || addr.boffset >= FIL_PAGE_DATAPXB-3372Satya Bodapati
- xtrabackup --stream does not exit on successPXB-3369Resolved issue: PXB-3369
- Fix jenkins test failuresPXB-3368Resolved issue: PXB-3368Satya Bodapati
- Documentation bug for xtrabackup 8.4.0PXB-3363Resolved issue: PXB-3363patrick.birch
- In which version does xtrabackup start to support PUNCH HOLE of mysql5.7?PXB-3362Resolved issue: PXB-3362
50 of
Improve the Error message thrown in case the JS code in stored function returns special number like Infinity, -Infinity or NaN.
General
Escalation
General
Escalation
Description
Environment
None
Details
Details
Assignee
Dmitry Lenev
Dmitry LenevReporter
parveez.baig
parveez.baigNeeds QA
Yes
Priority
Smart Checklist
Smart Checklist
Created February 18, 2025 at 9:48 AM
Updated March 25, 2025 at 3:11 PM
Activity
Show:
In JS function if there is division by zero then JS code returns Infinity which is of type Number. But the resulting datatype in mysql by the JS stored routine is of String type with value 'Infinity'. Hence if such error occurs in some function which has Integer return type and the resulting return value is Infinity we get the error "ERROR 1366 (HY000): Incorrect integer value: 'Infinity' for column 'test(231)' at row 1"
Better to have more meaningful error message maybe like out of range ERROR as we see in case the RETURN type is DOUBLE/FLOAT.
mysql> CREATE FUNCTION test(a INT) RETURNS INTEGER LANGUAGE JS AS $$ return 1/0; $$; Query OK, 0 rows affected (0.02 sec) mysql> SELECT test(1); ERROR 1366 (HY000): Incorrect integer value: 'Infinity' for column 'test(1)' at row 1 mysql> CREATE FUNCTION test2(a INT) RETURNS INTEGER LANGUAGE JS AS $$ return 0/0; $$;; Query OK, 0 rows affected (0.02 sec) mysql> SELECT test2(1); ERROR 1366 (HY000): Incorrect integer value: 'NaN' for column 'test2(1)' at row 1 mysql> CREATE FUNCTION test3(a INT) RETURNS INTEGER LANGUAGE JS AS $$ return -a/0; $$; Query OK, 0 rows affected (0.02 sec) mysql> SELECT test3(4); ERROR 1366 (HY000): Incorrect integer value: '-Infinity' for column 'test3(4)' at row 1