What commenters asked our summary
In our own words. Each line links to the comment it is based on.
- Whether the extension supports filtering documents by terms and then sorting by relevance score.From this comment
- How the implementation copes with frequent writes while keeping search latency low.From this comment
- When the extension will be offered on managed Postgres services.From this comment
- Whether this suits hybrid search that combines keyword and vector retrieval for RAG.From this comment
- Whether it is usable in practice and how it compares, since one team already runs it.From this comment
What they doubted or pushed back on our summary
- Ranking seems present but term filtering may be missing, limiting usefulness.From this comment
- A rival product being closed off was read as a negative signal about the company.From this comment
- Case-insensitive search remains awkward in Postgres generally, an unrelated but common complaint.From this comment
- Similar-sounding extension names create confusion between competing projects.From this comment
What the maker answered our summary
7 replies from the maker in the thread; the points below are the ones we could tie to a comment.
- Numeric-rank filtering was deprioritised because SQL workarounds exist, but it will be revisited.From this comment
- Write speed and search speed trade off, and tuning it is unfinished; bulk indexing was prioritised.From this comment
- Hybrid search was a main target use case, though plain keyword search also works.From this comment
- Partitioned tables are well supported, and expression indexes may come via a community pull request.From this comment
What a builder can take from it: Naming, managed-hosting availability and filtering flexibility decide adoption as much as raw benchmark speed, so plan for these early. our reading
The title, taken apart our calculation
This post got 203 points; the median for all 1442 posts is 112. In Developer tools (185 posts) the median is 106 points and 38 comments.
When it was posted our calculation
Tuesday at 16:00 UTC. Of 3,565 Show HN posts submitted in that UTC hour over the window (2025-11-20 to 2026-11-20), 146 (4.1%) reached 50 points; on Tuesdays it was 2.8% of 8,995. The average over all hours is 2.9%. One post's time does not explain its result; the full table of hours is on the Show HN hub.
Check your title our calculation
Type the title you plan to post. It is compared with 1,442 Show HN posts that reached 50 or more points: its length, its shape, and how posts of that length and shape did. Nothing is sent anywhere.
Type a title above to see where it sits.
Draft my Show HN post
Paste your site address and get title options and a first comment for your own Show HN post, written from what your site says and checked against the numbers above. Nothing is posted for you.
Free to try and no account needed. FoxPlug is for people who ship several projects and keep stalling on telling anyone: it turns what you ship into posts you approve before anything goes out. See what each plan includes.
More Developer tools teardowns
Points, comments, titles and times are Hacker News's own numbers, read from the post itself, last updated Nov 2026. Summaries of what people said are ours, written in our own words, and each one links to the comment it came from. Percentages and medians marked "our calculation" are computed from the posts counted on the page: they describe what happened, not what will happen to your post. FoxPlug posts nothing for you. Plans and limits are on the pricing page. Questions: support.
After the launch post: a changelog your users read
A launch brings visitors once. FoxPlug turns what you ship afterwards into a public changelog and ready posts, so the next visitor finds something new.
Start your changelog See a SaaS changelog example
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Visual cards and walkthrough videos made from what you shipped
- Posts for X, LinkedIn and dev.to written from your changes
- Connect GitHub and the tools you build with