PostgreSQL 19 now accepts lag(x) IGNORE NULLS, but MySQL doesn't. MySQL 9.7.4 parses the clause and then fails with ERROR 1235: "This version of MySQL doesn't yet support 'IGNORE NULLS'". Its manual says only RESPECT NULLS, the default, is permitted.
3
A Rust std Mutex stays poisoned after a panic: lock() keeps returning Err, although the data is still inside the PoisonError. Once you've repaired the data, Mutex::clear_poison() (stable since Rust 1.77) resets the flag and lock() returns Ok again.
7
Building Rust with panic = "abort" doesn't remove std::sync::Mutex's poison flag. The flag is compiled into the prebuilt standard library, which uses unwinding, so on Rust 1.100 for Apple Silicon Mutex<u64> is still 24 bytes. parking_lot's is 16.
5
PostgreSQL 19 adds effective_wal_level, the WAL level actually in use. With wal_level = replica it reads logical while any logical replication slot exists, including the temporary slot REPACK (CONCURRENTLY) creates for the duration of the command.
3
PostgreSQL 19's REPACK (CONCURRENTLY) refuses a table without a primary key: "has no identity index". A unique index on NOT NULL columns plus ALTER TABLE ... REPLICA IDENTITY USING INDEX is enough; on 19.0 the same command then succeeded.
4
Lazy map initialisation in a Go method with a value receiver (func (c Counter) Inc) never panics and never works: the method makes the map on a copy, so the struct's field is still nil after every call. Use a pointer receiver for methods that initialise fields.
7
pgx 5.13, the Go PostgreSQL driver, changed what database/sql reports for column metadata: an unconstrained varchar's Length went from -5 to math.MaxInt64, and timestamptz(3) now reports scale 3. Schema tools and code generators that read these values will see different output.
7
OpenAI's new 2h and 8h background windows in the Responses API cut model token rates by 30% and 40%. One catch from the docs: normal Standard requests can't reuse prompt cache entries those background requests created, even for an identical prompt.
1
1
16
ImportStatic retweeted
Happy to announce that we have migrated our service to pagesaver.ai
Running a SQLite script from Rust: rusqlite's execute_batch lets SQLite find statement boundaries, so a trigger body containing 'a;b' works. Splitting the script on ';' yourself fails with unrecognized token, and in rusqlite 0.43 a comment-only last piece is Error::Empty.
9
rusqlite 0.42 and 0.43 move to libsqlite3-sys 0.40, and Cargo allows only one crate linking sqlite3 per build. So rusqlite_migration 2.7 (needs rusqlite 0.41) or sqlx 0.9 in the same project blocks the upgrade; with sqlx 0.9 Cargo picks rusqlite 0.39.
3
In a Claude Code session with Code Mode on, a PreToolUse hook that reaches its timeout refuses the tool call ("the hook did not finish"). Outside Code Mode a timed-out hook lets the call through. Check the timeouts on slow policy hooks before trying it.
24
Rust's process::exit still runs C atexit handlers on 1.100, we checked. rust-lang/rust#165125, in final comment period, switches it to POSIX _exit, which skips them: C cleanup registered with atexit will stop running when Rust code calls process::exit.
11
The PostgreSQL 18.7 fix for CVE-2026-6460 adds a server parameter, composite_type_mismatch, and says C-language extensions must be rebuilt for full protection. On 18.6, SHOW composite_type_mismatch fails with "unrecognized configuration parameter", so it doubles as a patch check.
1
61
Of the eight Rust std memory safety bugs Microsoft FORGE reported, five are fixed in stable 1.97 to 1.100. Pattern becomes an unsafe trait in 1.102. The process::exit and exec fixes are still open.
1
20
Full write-up with the code: importstatic.com/rust/rust-s…
3
A PostgreSQL RLS policy with no TO clause applies to PUBLIC, and permissive policies are combined with OR. On PostgreSQL 18.6 one CREATE POLICY ... FOR SELECT USING (true) gave anon every row of a table that already had a per-user policy. Check pg_policies for qual = 'true'.
5
PostgreSQL takes a REPEATABLE READ transaction's snapshot at its first statement, not at BEGIN. In our PostgreSQL 18.6 run, a row another session updated after BEGIN but before the first SELECT was visible. A SELECT 1 right after BEGIN pins the snapshot.
5
With a custom allocator in Rust 1.100, Vec::push can't report that the allocator is full: our 256-byte arena printed "memory allocation of 256 bytes failed" and the process aborted (exit 134). Vec::try_reserve returns an error you can handle instead.
11
Go's "fatal error: concurrent map writes" bypasses recover() and exits the process. The runtime check is also best-effort: four racing writes crashed once in five runs. Run tests with -race.
1
7
Full write-up with the code: importstatic.com/go/go-concu…
6

