All issues

Search results

Temporary sequences remain visible across frontend connections

Status: Open.

#1671 In pgdogdev/pgdog;

· apkipa opened on Sep 27, 2026

Cached named Parse is accepted in an aborted transaction

Status: Open.

#1670 In pgdogdev/pgdog;

· apkipa opened on Sep 26, 2026

Make shard key decoding more robust

Status: Open.

Task

#1668 In pgdogdev/pgdog;

· sgrif opened on Sep 25, 2026

[Prepared statements] Add data from pg_prepared_statements into SHOW PREPARED

acceptedThe issue is added to our backlog.The issue is added to our backlog.

Status: Open.

Feature

#1640 In pgdogdev/pgdog;

· levkk opened on Sep 24, 2026

Rewrite ND transaction-time functions in SELECT as well

Status: Open.

Bug

#1624 In pgdogdev/pgdog;

· jkaczman opened on Sep 23, 2026

[Query engine] Use lazy cross-shard connections

Status: Open.

Feature

#1623 In pgdogdev/pgdog;

· levkk opened on Sep 23, 2026

·  

Sharding 1.0

Recovery Sync commits an implicit transaction after frontend disconnect

Status: Open.

Bug

#1621 In pgdogdev/pgdog;

· apkipa opened on Sep 23, 2026

[Sequences] Global monotonic i32 sequence doesn't account for schema name

Status: Open.

Bug

#1606 In pgdogdev/pgdog;

· levkk opened on Sep 21, 2026

·  

Sharding 1.0

[Resharding] Replication is slow

Status: Open.

Bug

#1605 In pgdogdev/pgdog;

· levkk opened on Sep 21, 2026

·  

Sharding 1.0

Replace aws-sigv4 crate with FIPS-compliant crypto alternative

Status: Open.

#1604 In pgdogdev/pgdog;

· jkaczman opened on Sep 21, 2026

[Resharding] Replay DDL on destination shards

Status: Open.

Feature

#1603 In pgdogdev/pgdog;

· levkk opened on Sep 21, 2026

·  

Sharding 1.0

Enable validation for FK constraint during resharding

reshardingRe-sharding of databases.Re-sharding of databases.

Status: Open.

Feature

#1601 In pgdogdev/pgdog;

· meskill opened on Sep 21, 2026