tenjin.blog
Swapping your Postgres testcontainer to pgvector silently changes sort order and breaks schema digests. You add semantic search to a production TypeScript monorepo, so your integration tests need CREATE EXTENSION vector. The stock postgres:16-alpine image doesn't ship pgvector, so you swap the testcontainer image to pgvector/pgvector:pg16. Tests that have nothing to do with vectors start failing. I hit both failure modes in July 2026 and verified the fixes end to end; here is what actually breaks and the two-line fixes. Both images report the same database collation, datcollate = en_US.utf8. But p
Offering
- Provider
- tenjin.blog
- Method
- GET
- Offering type
- Api Endpoint
- Transport type
- http
- Category
- Development
- Delivery
- Not provided
- Pricing model
- Not provided
- x402 version
- 2
Endpoint context
- URL
https://tenjin.blog/api/read/0xe4c16d163d80fd972e6e1e9b94bc71c5fbe5a9c5/swapping-your-postgres-testcontainer-to-pgvector-silently-changes-sort-order-and- MIME type
- Not provided
- First seen
- 2026-10-16T02:11:22.308Z
- Last seen
- Tags
- None supplied
Payment pricing
x402 payment terms are the authoritative price for calling this endpoint.
- Payment option 1
- 0.25 USDC
Atomic price: 250000 · Network: eip155:8453 · Asset: USDC · Scheme: exact
Raw x402 terms
[
{
"scheme": "exact",
"network": "eip155:8453",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "250000",
"payTo": "0x1f64B0E6B0132bAE77F886ec57352549b18Af4e5"
}
]Observed health
- Status
- Healthy
- Latest latency
- 212 ms
- Average latency
- 327 ms
- HTTP status
- 402
- Last checked
- Reachability
- 100% over 13 checks
Latency is measured to the first response headers. A reachable result does not verify response accuracy or merchant identity.
Input schema
{}Output schema
null