Skip to content

NOTIFY size limit and scaling concerns #1

@14113

Description

@14113

First of all, thank you for creating and sharing this gem! I really like the improvements it brings, and I value the effort that went into it. I tried it out on our staging environment and ran into a couple of things that might be worth discussing:

  1. Response too large for PostgreSQL NOTIFY
    When I request the list of tools, I hit the following error:
    MCP error -32001: Response too large for PostgreSQL NOTIFY. Try requesting a smaller page size.
    It looks like the payload can easily exceed the limits of PostgreSQL's NOTIFY mechanism. I can cut some description, but it's useful for AI.
Image
  1. Scaling considerations
    I also wanted to mention possible scaling concerns. The current approach is simple and effective, but I’m not sure how it will behave under higher load in production. This article explains some of the limitations in more detail:
    https://www.recall.ai/blog/postgres-listen-notify-does-not-scale

Overall, I really like the direction of the gem. These are just a few observations from my initial testing that might be useful for future iterations.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions