Skip to main content
LangChainCustomer feedback

A company building a natural language query tool evaluated a custom text-to-SQL solution with Langchain but concluded it would require too much effort to build and maintain.

What happened

Post: "Natural language querying on top of PG for non tech users"

Source

RedditSep 27, 2026By u/Glitch_In_The_Data

r/PostgreSQL

Natural language querying on top of PG for non tech users

upvotes
0
comments
17

Post

Highlighted: the lines this signal was extracted from

Building an app for the operations team that runs on Postgres. Business side wants to query in plain English without writing sql. Our table metadata is not rich. Tried a couple of options so far. Setup syncs our Postgres tables into Databricks and then using Genie agents to generates sql on the fly. Works well for straightforward questions but gets shaky on anything that needs multiple business logic that isn’t obvious from column names. Custom option using text2sql with Langchain, which gives better control but is a lot more to build and maintain. And we will eventually move all workloads to cloud. What’s better in practice? How to deal with the metadata gap? A colleague keeps talking about Metabase for this kind of self service. Is it worth considering?

reddit.com/r/PostgreSQL/comments/1wrmstn/natural_language_querying_on...Read the full source

Comments on the post

5 of 17 comments
  • “I don't have any tool ideas, but my experience has been that business users (analysts even) do not have the ability to precisely phrase a logical question that doesn't need some additional prompting and refinement to be usable for the purpose they have in mind. I'd be interested in hearing the experiences of others, but this has always struck me as being the reason why natural language querying”

    u/Zestyclose-Turn-35763 points · Sep 27, 2026View

  • “business logic that isn’t obvious from column names This is true for anything and anyone, if you're just guessing, what kind of result do you expect if you don't provide the information needed to understand the data? Chucking a bunch of undocumented data over a fence isn't going to magically solve all your problems for you. A good first step is adding detailed column descriptions, registering”

    u/CrayonUpMyNose2 points · Sep 27, 2026View

  • “Should we buy stock in Metabase, whatever that is?”

    u/RevolutionaryRush7172 points · Sep 27, 2026View

  • “Crazy idea: teach someone SQL.”

    u/aquisalid1 points · Sep 27, 2026View

  • “"Our table metadata is not rich." That is your real problem, and no SQL can solve it for you. You have to fix your documentation first. This is where AI can help you: document the application (where you have the business logic) and the database. Expect this to be a big project, but it's fundamental for future natural language querying by non-tech users. It also helps you to find (and prevent) bu”

    u/elevarq1 points · Sep 27, 2026View

Extracted by Autobound

From the Signal API record
Signal
Customer feedback

What this signalsUser posts often show product pain before it reaches reviews or churn.

Subreddit
r/PostgreSQL
Stage
Considering

Companies

  • DatabricksAlso named
  • MetabaseAlso named

The full record

From the Signal API record

Numbers

Mentions
7

Details

Timing
Completed
Category
Implementation
Virality
Low
Post kind
Text
Prominence
Core
Company's role
Vendor

Topics and mentions

Topics

  • text-to-sql
  • natural language query
  • development framework
  • maintenance

Flair

  • How-To

Extraction

Sentiment
Negative
Detected
Sep 27, 2026
signal_type
reddit-company
signal_subtype
customerFeedback

Use this data

Get every Reddit signal for LangChain and the companies you sell to, in the tools you already use.

  1. Ask Claude about it

    Connect Autobound to Claude, Claude Code or Cursor with MCP. Then ask: “What changed at LangChain this week?”

  2. Send it to your own tools

    The Signal API returns Reddit signals for any list of companies as JSON, for your CRM, warehouse or app.

  3. Try it free

    Sign up and spend your free credits on the companies you sell to.

    Start Free1,000 free credits

The API returns more than this page shows

This page shows a preview. The full reddit-company record in the Signal API and MCP can also have these 8 fields. Some fields are empty for some signals.

Company

  • linkedin_urlValue in the API
  • industriesValue in the API
  • employee_count_lowValue in the API
  • employee_count_highValue in the API
  • revenueValue in the API
  • descriptionValue in the API

Signal

  • signal_nameValue in the API
  • associationValue in the API
Show the full JSONThe record on this page and the API request

GET /v1/signals/d8358ad0-373a-50fa-a593-6acd777cdb7d returns this record as JSON. POST /v1/companies/enrich returns every signal for langchain.com.

{
  "signal_id": "d8358ad0-373a-50fa-a593-6acd777cdb7d",
  "signal_type": "reddit-company",
  "signal_subtype": "customerFeedback",
  "detected_at": "2026-09-27T15:17:23+00:00",
  "company": {
    "name": "LangChain",
    "domain": "langchain.com"
  },
  "data": {
    "nsfw": false,
    "stage": "considering",
    "awards": 0,
    "timing": "completed",
    "topics": [
      "text-to-sql",
      "natural language query",
      "development framework",
      "maintenance"
    ],
    "post_id": "1wrmstn",
    "summary": "A company building a natural language query tool evaluated a custom text-to-SQL solution with Langchain but concluded it would require too much effort to build and maintain.",
    "category": "implementation",
    "comments": [
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pcdt7z3/",
        "depth": 0,
        "score": 3,
        "author": "Zestyclose-Turn-3576",
        "excerpt": "I don't have any tool ideas, but my experience has been that business users (analysts even) do not have the ability to precisely phrase a logical question that doesn't need some additional prompting and refinement to be usable for the purpose they have in mind.\n\n I'd be interested in hearing the experiences of others, but this has always struck me as being the reason why natural language querying",
        "posted_at": "2026-09-27T15:30:53.000Z",
        "author_url": "https://www.reddit.com/user/Zestyclose-Turn-3576/"
      },
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pce06wa/",
        "depth": 0,
        "score": 2,
        "author": "CrayonUpMyNose",
        "excerpt": "business logic that isn’t obvious from column names\n\n This is true for anything and anyone, if you're just guessing, what kind of result do you expect if you don't provide the information needed to understand the data? Chucking a bunch of undocumented data over a fence isn't going to magically solve all your problems for you.\n\n A good first step is adding detailed column descriptions, registering",
        "posted_at": "2026-09-27T16:00:35.000Z",
        "author_url": "https://www.reddit.com/user/CrayonUpMyNose/"
      },
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pcduvqu/",
        "depth": 0,
        "score": 2,
        "author": "RevolutionaryRush717",
        "excerpt": "Should we buy stock in Metabase, whatever that is?",
        "posted_at": "2026-09-27T15:38:01.000Z",
        "author_url": "https://www.reddit.com/user/RevolutionaryRush717/"
      },
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pce6ytk/",
        "depth": 0,
        "score": 1,
        "author": "aquisalid",
        "excerpt": "Crazy idea: teach someone SQL.",
        "posted_at": "2026-09-27T16:29:14.000Z",
        "author_url": "https://www.reddit.com/user/aquisalid/"
      },
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pcedar9/",
        "depth": 0,
        "score": 1,
        "author": "elevarq",
        "excerpt": "\"Our table metadata is not rich.\"\nThat is your real problem, and no SQL can solve it for you. You have to fix your documentation first. This is where AI can help you: document the application (where you have the business logic) and the database. Expect this to be a big project, but it's fundamental for future natural language querying by non-tech users.\n\n It also helps you to find (and prevent) bu",
        "posted_at": "2026-09-27T16:55:42.000Z",
        "author_url": "https://www.reddit.com/user/elevarq/"
      },
      {
        "url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/comment/pcfdaqm/",
        "depth": 0,
        "score": 1,
        "author": "ibraaaaaaaaaaaaaa",
        "excerpt": "There are much more things going in these fed keywords than DDLs, and speaking from perspective of someone who built something similar, the moment it spits one time not accurate number, it loses its credibility",
        "posted_at": "2026-09-27T19:17:56.000Z",
        "author_url": "https://www.reddit.com/user/ibraaaaaaaaaaaaaa/"
      }
    ],
    "evidence": [
      "[post] Tried a couple of options so far.",
      "[post] Custom option using text2sql with Langchain, which gives better control but is a lot more to build and maintain."
    ],
    "virality": "low",
    "post_date": "2026-09-27T15:17:23.000Z",
    "post_kind": "text",
    "post_text": "Building an app for the operations team that runs on Postgres. Business side wants to query in plain English without writing sql. Our table metadata is not rich. Tried a couple of options so far.\n\nSetup syncs our Postgres tables into Databricks and then using Genie agents to generates sql on the fly. Works well for straightforward questions but gets shaky on anything that needs multiple business logic that isn’t obvious from column names.\n\nCustom option using text2sql with Langchain, which gives better control but is a lot more to build and maintain. And we will eventually move all workloads to cloud.\n\nWhat’s better in practice? How to deal with the metadata gap?\n\nA colleague keeps talking about Metabase for this kind of self service. Is it worth considering?",
    "sentiment": "negative",
    "subreddit": "PostgreSQL",
    "post_flair": [
      "How-To"
    ],
    "post_title": "Natural language querying on top of PG for non tech users",
    "prominence": "core",
    "source_url": "https://www.reddit.com/r/PostgreSQL/comments/1wrmstn/natural_language_querying_on_top_of_pg_for_non/",
    "entity_role": "vendor",
    "post_author": "Glitch_In_The_Data",
    "upvote_ratio": 0.2,
    "mention_count": 7,
    "mention_surge": true,
    "subreddit_url": "https://www.reddit.com/r/PostgreSQL/",
    "total_upvotes": 0,
    "comments_total": 17,
    "total_comments": 17,
    "other_companies": [
      {
        "name": "Databricks",
        "role": "alternative",
        "domain": "databricks.com"
      },
      {
        "name": "Metabase",
        "role": "alternative",
        "domain": "metabase.com"
      }
    ],
    "post_author_url": "https://www.reddit.com/user/Glitch_In_The_Data/",
    "signal_category": "feedback",
    "comments_included": 6
  }
}

Long text fields are shortened on this page.

Looking up one signal by its id is free. Enrich costs 2 credits per signal returned; a call with no results is free.