chronoskin
stable 4.2.0 next 4.3.0-rc.1 lts 3.9.14 Released 3 days ago read the notes →
Changelog and engineering notes

What shipped, and why

Every release of the chronoskin query engine, with the reasoning behind it. A new version most Thursdays.

One e-mail per release, no marketing.Or take the feed

latest release13 Mar 2025

v4.2.0 Minor

Streaming query plans, and a planner that no longer guesses.

  • added14
  • changed9
  • fixed23
$ chronoskin upgrade 4.2.0 Release notes

From the engineering notes

All posts
  • 41releases in the last twelve months
  • 612fixes shipped since version 4.0
  • 137people with a merged change
  • 0breaking changes in the 4.x line

Recent releases

newest first
  1. 13 Mar 2025v4.2.0
    Streaming query plans

    Plans are sent to the client while the query runs, so a slow step shows up before the result does. The planner now samples instead of assuming.

    NewPlanner14 added, 23 fixed
  2. 27 Feb 2025v4.1.3
    Connection pool fixes

    Idle connections are closed after the timeout you set, not the default. Fixes a leak seen under bursty load.

    FixDriver6 fixed
  3. 13 Feb 2025v4.1.2
    Slow writes on large batches

    A lock was held across the whole batch. It is now taken per page. Read the postmortem for the forty minutes this cost us.

    FixStorage2 fixed
  4. 30 Jan 2025v4.1.0
    Vectorised hash joins

    Joins on integer keys run in batches of 1,024 rows. The join_batch setting from 4.0 is deprecated and will be removed in 5.0.

    NewDeprecation8 added, 11 fixed
All 41 releases

Release lines

supported
  • Stable4.2.0
  • Next4.3.0-rc.1
  • Long term3.9.14
  • End of life3.8, 30 Jun

Still on 3.9?

The upgrade guide walks through the four settings that changed and the one that is gone.

Read the guide
feedatom
# every release, as it ships
GET /changelog/feed.xml
200  41 entries
  1. Changelog
  2. 4.x
  3. v4.2.0

Streaming query plans

v4.2.0New13 Mar 2025, 46 commits

The plan arrives while the query runs, and the planner samples your data instead of assuming its shape.

What changed in 4.2

Until now a plan was something you asked for after a query had been slow. From this release it is a stream you can watch.

Set plan.stream on a session and every step reports its row count and timing as it finishes. The driver exposes it as an iterator, so no polling is needed.

Added

  • Streaming plans over the wire protocol, version 7 and later
  • Sampled histograms for every indexed column, refreshed nightly
  • A --explain-live flag in the command line client

Changed defaults

The sample rate defaults to 1 percent. Tables under 10,000 rows are read in full.

chronoskin.toml3 lines changed
@@ planner @@  [planner]- selectivity = 0.1- join_batch  = 256+ statistics  = "sampled"+ sample_rate = 0.01  timeout     = "30s"@@ session @@  [session]+ plan.stream = true

Packages in this release

size in kB
PackageFromToSizeChange
chronoskin-server4.1.34.2.018,420+212
chronoskin-planner4.1.34.2.03,904+388
chronoskin-cli4.1.04.2.06,118+41
driver-node7.3.17.4.0212+9
driver-go2.8.02.9.01,046-17
Checksums are in the release archive.Earlier versions

This release

Stable
  • Released13 Mar 2025
  • Commits46
  • Protocol7
  • Supported untilMar 2026

Contributors

11
upgradezsh
$ chronoskin upgrade 4.2.0
checking 4 settings
ok  no manual steps
$ chronoskin restart --rolling

Running a release candidate?

4.3.0-rc.1 already has everything on this page, plus partial indexes behind a flag.

See the next line
  1. Changelog
  2. Archive

Every release

All 41 versions of the last twelve months, with what each one added, changed and fixed.

Labels

Minor New Planner Fix Deprecation Breaking
Showing the 4.x line
VersionTitleKindDateChanges
v4.2.0Streaming query plansMinor13 Mar 202546
v4.1.3Connection pool fixesFix27 Feb 20256
v4.1.2Slow writes on large batchesFix13 Feb 20252
v4.1.1Timezone names in exportsFix6 Feb 20254
v4.1.0Vectorised hash joinsMinor30 Jan 202531
v4.0.4Replica lag reportingDeprecation16 Jan 202512
v4.0.3Index builds resume after restartFix9 Jan 20257
7 of 18 releases

No security releases in the 4.x line

When one ships it is listed here first and sent to every subscriber the same hour.

Get security notices
  1. Changelog
  2. Subscribe

Follow the releases

By e-mail or by feed. Choose what you hear about and how often.

Security releases are always sent. They ignore the frequency you pick below.

We could not confirm that address. Check it and send the form again.

By e-mail

one click to leave
Cancel
Feedsxmljson
# all releases
/changelog/feed.xml
# one release line
/changelog/4.x/feed.xml
# security releases only, as JSON
/changelog/security.json
$ curl -s chronoskin.dev/changelog/latest | jq .version

Your subscription

Unconfirmed

Every release and the engineering notes, to one address. The last e-mail was v4.2.0 on 13 March.