pgrs.net valid
Paul Gross's Blog
Technical blog by Paul Gross, a Principal Software Engineer with expertise in payments, PostgreSQL, high availability systems, and developer tools.
For agents: Technical blog by Paul Gross, principal engineer, with articles on PostgreSQL migrations, scaling, high availability and payments.
postgresqlschema migrationshigh availabilitypayments engineeringdeveloper tools
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-26T11:23:33.678Z. Cached copy · Source on pgrs.net
# Paul Gross's Blog
> Technical blog by Paul Gross, a Principal Software Engineer with expertise in payments, PostgreSQL, high availability systems, and developer tools.
## About the Author
Paul Gross is a Principal Software Engineer based in Seattle. He has worked at Rvvup, Ripple, Braintree/PayPal, and ThoughtWorks. Now, he primarily does independent consulting. His expertise spans payments systems, database scaling, high availability architecture, and developer productivity.
- Website: https://www.pgrs.net
- GitHub: https://github.com/pgr0ss
- Twitter: https://twitter.com/pgr0ss
- LinkedIn: https://www.linkedin.com/in/pgr0ss/
- Mastodon: https://hachyderm.io/@pgr0ss
- Bluesky: https://bsky.app/profile/pgr0ss.bsky.social
## Key Topics
- PostgreSQL scaling, operations, and best practices
- Payment systems architecture and lessons learned
- Double-entry ledgers and financial software
- High availability and zero-downtime deployments
- DuckDB for data analysis
- Developer tools and productivity
## Notable Articles
### PostgreSQL & Databases
- [Safe Operations For High Volume PostgreSQL](https://www.pgrs.net/2014/05/14/safe-operations-for-high-volume-postgresql/): Practical guide to running schema migrations without downtime on high-traffic PostgreSQL databases. Covers safe vs unsafe operations and workarounds.
- [Scaling PostgreSQL at Braintree: Four Years of Evolution](https://www.pgrs.net/2012/10/16/scaling-postgresql-at-braintree-four-years-of-evolution/): Journey from MySQL to PostgreSQL, implementing sharding, and moving from DRBD to streaming replication.
- [Two Exciting PostgreSQL Features to Improve Null Handling](https://www.pgrs.net/2023/11/14/two-exciting-postgresql-features-to-improve-null-handling/): Coverage of IS DISTINCT FROM and NULLS NOT DISTINCT features.
- [DuckDB as the New jq](https://www.pgrs.net/2024/03/21/duckdb-as-the-new-jq/): Using DuckDB for command-line JSON and CSV processing.
- [DuckDB over Pandas/Polars](https://www.pgrs.net/2024/11/01/duckdb-over-pandas-polars/): Why SQL with DuckDB can be simpler than Pandas/Polars for data analysis.
### Payments & Ledgers
- [Lessons Learned From Payments Startups](https://www.pgrs.net/2024/01/26/lessons-learned-from-payments-startups/): Comprehensive guide covering modular monoliths, continuous deployment, testing strategies, decision logs, and the job drain pattern.
- [Double-Entry Ledgers: The Missing Primitive in Modern Software](https://www.pgrs.net/2025/06/17/double-entry-ledgers-missing-primitive-in-modern-software/): Why ledger modeling should be used more widely, with examples for payments, reward points, and more.
- [pgledger: Ledger Implementation in PostgreSQL](https://www.pgrs.net/2025/03/24/pgledger-ledger-implementation-in-postgresql/): Introduction to pgledger, a pure PostgreSQL double-entry ledger implementation.
- [pgledger in PostgreSQL is Fast](https://www.pgrs.net/2025/05/16/pgledger-in-postgresql-is-fast/): Performance benchmarks showing pg
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| commandprompt.com | Home | documentation Data and analytics | US | 61 | ✓ | ✓ | |
| vonng.com | VONNG | documentation Data and analytics Personal sites and blogs | — | 45 | ✓ | ||
| yugabyte.com | YugabyteDB | documentation Data and analytics Databases +1 | US | 63 | ✓ | ✓ | |
| severalnines.com | Severalnines | documentation Databases DevOps and observability | SE | 58 | ✓ | ||
| pgedge.com | pgEdge | documentation AI and machine learning Data and analytics +2 | — | 56 | ✓ | ||
| pigsty.io | PIGSTY | documentation Data and analytics Databases +1 | — | 48 | ✓ | ||
| vela.run | Vela | transactional Data and analytics Infrastructure +1 | — | 48 | ✓ | ✓ | |
| riverqueue.com | River | documentation Developer tools Infrastructure | — | 48 | ✓ | ✓ |
Machine-readable: GET /v1/resolve?q=pgrs.net · GET /v1/domain/pgrs.net · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage pgrs.net, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for pgrs.net:
1. POST https://agentwebmap.com/v1/sites/pgrs.net/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://pgrs.net/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/pgrs.net/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/pgrs.net).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.