You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
OS: Linux Debian 12
PHP: 8.1
php-mysql-replication: 7.0.1
8.0.27 - Oracle MYSQL
On a rare occasion, maybe once every 1000 times, an INSERT event will be triggered by php-mysql-replication, but an immediate SELECT query on the unique ID (passed in the insert values) will return no rows.
The same SELECT query will return a row if subsequently entered manually.
Is the INSERT event first sent to the binlog and THEN to the actual MySQL engine? It feels like there's a race condition there.
Transactions are not used in this particular scenario.
The text was updated successfully, but these errors were encountered:
OS: Linux Debian 12
PHP: 8.1
php-mysql-replication: 7.0.1
8.0.27 - Oracle MYSQL
On a rare occasion, maybe once every 1000 times, an INSERT event will be triggered by php-mysql-replication, but an immediate SELECT query on the unique ID (passed in the insert values) will return no rows.
The same SELECT query will return a row if subsequently entered manually.
Is the INSERT event first sent to the binlog and THEN to the actual MySQL engine? It feels like there's a race condition there.
Transactions are not used in this particular scenario.
The text was updated successfully, but these errors were encountered: