Skip to content

Commit 401137e

Browse files
Version Packages (#1043)
Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
1 parent af37b02 commit 401137e

3 files changed

Lines changed: 12 additions & 12 deletions

File tree

.changeset/fix-move-in-lsn-filtering.md

Lines changed: 0 additions & 11 deletions
This file was deleted.

packages/pglite-sync/CHANGELOG.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,16 @@
11
# @electric-sql/pglite-sync
22

3+
## 0.6.4
4+
5+
### Patch Changes
6+
7+
- af37b02: Fix move-in messages from tagged_subqueries not being synced
8+
9+
This fixes two issues with move-in messages from Electric's `tagged_subqueries` feature:
10+
11+
1. **LSN filtering bypass**: Move-in messages don't include an LSN header because they originate from direct database queries rather than the PostgreSQL replication stream. Previously, these messages were being filtered out as "already seen" because the missing LSN defaulted to 0. This fix checks for the `is_move_in` header and bypasses LSN filtering for these messages.
12+
2. **Duplicate key handling**: Move-in data can overlap with data from the initial sync (e.g., when a row "moves in" to match a subquery that it already matched during initial sync). This fix uses `ON CONFLICT DO UPDATE` for move-in inserts to handle these duplicates gracefully, updating the row with the latest data instead of erroring.
13+
314
## 0.6.3
415

516
### Patch Changes

packages/pglite-sync/package.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "@electric-sql/pglite-sync",
3-
"version": "0.6.3",
3+
"version": "0.6.4",
44
"description": "Postgres Sync for PGlite",
55
"type": "module",
66
"private": false,

0 commit comments

Comments
 (0)