Skip to content

Conversation

@fredzqm
Copy link
Contributor

@fredzqm fredzqm commented Jan 21, 2026

Description

Fix #9756

Before v15.2.1, FDC emulator uses prepared statement with pglite.

pglite has numerous limitations & bugs with prepared statement protocol. (Refer to electric-sql/pglite#223)

  • If an invalid SQL statement is prepared with pglite, its response crash the *sql.DB driver.
  • If there are multiple prepared statements, the prepared statement are mixed up.
    We ended up adding a maxOpenConnections: 1 to work around it.
    With prepared statement, all queries are routed to the same connection.

At v15.3.0, FDC switched to avoid prepared statement with pglite, hoping to get around pglite limitations.

  • It properly returns "pg error message" for any invalid SQL. Essential for direct SQL launch.
  • However, without prepared statement, *sql.DB.Begin() tries to spin up a new connection and get stuck due to maxOpenConnections: 1.

Scenarios Tested

Sample Commands

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @fredzqm, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses a critical bug where the Data Connect emulator would hang during transactions when using PGlite. The fix involves an internal change to how the emulator interacts with PGlite, specifically by removing a previous limitation on the number of open connections. This change ensures smoother and more reliable operation of the Data Connect emulator with PGlite by allowing multiple concurrent connections now that prepared statements are no longer an issue.

Highlights

  • PGlite Transaction Hang Fix: This PR resolves a transaction hang bug in the Data Connect emulator when interacting with PGlite by modifying how database connections are managed.
  • PGlite Connection Limit Removal: The maxOpenConnections: 1 limit for PGlite connections in the Data Connect emulator has been removed. This is now possible because the emulator has been updated to avoid prepared statements, which previously necessitated the single-connection restriction.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request fixes a transaction hang bug in the Data Connect emulator when using PGlite by allowing multiple connections. The change removes the maxOpenConnections: 1 setting, and the rationale is well-documented in a comment. My review includes a suggestion to improve code readability by relocating this comment.

@fredzqm fredzqm requested a review from joehan January 21, 2026 05:05
@fredzqm fredzqm merged commit ac7ca0b into main Jan 21, 2026
46 of 47 checks passed
@fredzqm fredzqm deleted the fz/txn-pglite branch January 21, 2026 15:36
MichaelDoyle pushed a commit that referenced this pull request Jan 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Data Connect Emulator v3.0.2 Transaction Mutation Hang

2 participants