v0.1.46

Breaking change

PgDog now blocks UPDATE queries that mutate a sharding key in a table that has foreign key references to other tables
that automatically mutate the referenced tables using:

• CASCADE
• SET NULL

Both of these were previously breaking referential integrity, since we were not moving the referenced rows. RESTRICT (which is typically default) is not affected because Postgres is able to validate ref integrity before we move the row.

Changelog

• feat(sharding): rewrite [[sharded_mappings]] config to make it easier to use @meskill (not documented yet, old config format still works)
• feat: add query_size_limit setting to block/warn on very large queries @meskill
• feat: RELOAD keeps connections and paused state if adding or removing connection databases or users @murex971
• feat(load balancer): add prefer_primary read/write separation mode to allow manual opt into load balancing @stewart-glabs
• feat: log warning when lsn_check_delay is misconfigured
• refactor: start porting the codebase to use the new, much faster SQL parser @sgrif
• feat(sharding): block cross-shard sharding key updates on tables that have foreign key constraints @murex971
• feat(auth): Hashicorp Vault server authentication integration @larrywax

New Contributors

• @stewart-glabs made their first contribution in #1090
• @larrywax made their first contribution in #958

Full Changelog: v0.1.45...v0.1.46