AI Weekly Malaysia

Summaries

Short AI and tech summaries with source links, signal scores, and why each update matters for builders, founders, and Malaysian tech workers.

Reset

Showing 1-2 of 2 results

DateProviderScoreSummary
20 Nov 2026, 4:43 AMSimon Willison8.0 PostgreSQL 19 Released

PostgreSQL 19 shipped on 19 November 2026, roughly two months later than the usual September cadence, which Simon Willison attributes mainly to the volume of issues the PostgreSQL team had to work through during what he calls the ongoing 'AI-reported vulnerability apocalypse.' His favourite feature is the new WAIT FOR LSN command: a session on a standby can call WAIT FOR LSN '0/0306EE20' WITH (TIMEOUT '0.1s') to block until that standby has replayed WAL up to a given LSN before reading, giving applications read-your-writes consistency when reads go to replicas. The LSN is obtained from the primary via pg_current_wal_insert_lsn() and can be stashed client-side, e.g. in a signed cookie — the same pattern Wikipedia's MediaWiki implements by hand against MySQL replication using WAIT_FOR_EXECUTED_GTID_SET().

Why: If you scale reads by sending them to standbys, you currently either pin a user to the primary for a while after they write or accept stale reads; WAIT FOR LSN lets you keep replica reads and just pay a bounded wait (your TIMEOUT, e.g. 0.1s) after a write, so the decision shifts from 'route this user to primary' to 'how much lag can this request tolerate before erroring'. Note the source only details this one feature — don't assume the rest of PG19 from this post, and budget time to read the actual release notes before upgrading, given the release slipped two months over a heavy security-fix load.

19 Nov 2026, 4:14 PMThe Hacker News3.0 Researcher Demonstrates Database RCE Exploits Affecting PostgreSQL, MySQL and Oracle

The item is headlined as a researcher demonstrating remote code execution exploits against PostgreSQL, MySQL, and Oracle. The supplied article text contains only the page title and site navigation, with no affected versions, exploit prerequisites, CVE identifiers, disclosure timeline, or vendor response. It therefore does not substantiate the claim beyond the headline.

Why: You cannot make a concrete patch, upgrade, or configuration decision from this text because it does not say which PostgreSQL, MySQL, or Oracle versions are affected, what access or setup the exploit requires, or whether fixes are available. Treat it as an unverified headline until the technical details are published.

Top