pgdogdev/pgdog v0.1.60

on GitHub

Performance

• 40% faster handling of SELECT in sharded queries by removing redundant AST walks @jkaczman

Bugs

• 0.0 and -0.0 hashed to the same value, which broke DISTINCT, count() and other cross-shard functions @MaxFreedomPollard
• session_replication_role should be set via SET command @levkk
• interval type wasn't correctly parsed for some edge cases in cross-shard aggregates @dipeshbabu
• stddev / variance failed on some NULL values in cross-shard aggregates @dipeshbabu
• count() wouldn't preserve original input type / would cast everything to bigint @dipeshbabu
• NULL was incorrectly handled in array elements in cross-shard queries @dipeshbabu
• timestamp(tz) infinite values were not correctly parsed in cross-shard queries @dipeshbabu
• timestamp(tz) fractional time wasn't correctly preserved in cross-shard queries @dipeshbabu
• jemalloc would crash on ARM targets with page size >= 16k @dipeshbabu
• client/server TLS wouldn't load the whole chain, so client keys signed by intermediates were rejected @dipeshbabu
• don't run 2pc on direct-to-shard write transactions @rlittlefield
• connection pool statistics are preserved on RELOAD @murex971
• handle numeric infinite values correctly in cross-shard queries @dipeshbabu
• fully-qualified columns were skipped in DISTINCT ON @jkaczman
• sequence names are quoted to make sure they work with all table names @dipeshbabu
• don't drop SET check_function_bodies in schema sync @meskill
• pg deparser wasn't handling timezone operations correctly @meskill
• correctly route advisory lock calls in sharded deployments & handle the two parameter variant @jkaczman
• correctly track pg_catalog.pg_advisory_* fully qualified advisory lock calls @dipeshbabu

Code quality

• migrate replication/resharding to new tasks API @meskill
• unique_id and insert_splits cleanup @sgrif
• auto retries to some flaky spots in CI @jkaczman

New Contributors

• @MaxFreedomPollard made their first contribution in #1507

Full Changelog: v0.1.59...v0.1.60