tudorg

7 ms·

31.
Coding agent using Postgres copy-on-write branches(xata.io)
1 points by tudorg 10mo ago|0 comments
32.
Building a coding agent that uses Postgres branches(xata.io)
2 points by tudorg 10mo ago|0 comments
33.
Tips for Configuring Neovim for Claude Code(xata.io)
4 points by tudorg 10mo ago|0 comments
34.
Don't give Postgres too much memory(vondra.me)
5 points by tudorg 11mo ago|0 comments
35.
by tudorg 1y ago
Thanks for the report!
36.
Going down the rabbit hole of Postgres 18 features(xata.io)
56 points by tudorg 1y ago|5 comments
37.
by tudorg 1y ago
Lots of good improvements, my favorites are Oauth, NOT NULL constraint with NOT VALID, uuidv7, RETURNING contains old/new. And I think the async IO will bring performance benefits, although maybe not so much immediately.
38.
by tudorg 1y ago
Great to see pgstream on HN! Besides DDL changes, pgstream can also do on-the-fly data anonymization and data masking. It can stream to other stores, like Elasticsearch, but the current main focus is on PG to PG replication with DDL changes
39.
From DBA to DB Agents(xata.io)
1 points by tudorg 1y ago|0 comments
40.
by tudorg 1y ago
Check out Xata.io. A `xata.micro` instance is ~$9 per month (+storage). It’s in private beta but I can give you access if you are interested.
41.
by tudorg 1y ago
Ah yes, it was a typo, sorry.
42.
by tudorg 1y ago
For a tooling solution for this problem, and many others, pgroll ( https://github.com/xataio/pgroll ) automates the steps from the blog post in a single higher-level operation. It can do things like adding a hidden colum
43.
by tudorg 1y ago
That is correct, for non-volatile default values Postgres is quick, which means that it is generally a safe operation. Also interesting, `now()` is non-volatile because it's defined as "start of the transaction". So if you ad
44.
by tudorg 1y ago
[author] My point was that using the default config for the other providers while you control yours is a weakness in the methodology, and might influence the results. Note that when strictly limiting to 4 CPU it's still faster.
45.
by tudorg 1y ago
Another way to mitigate this is to make the agents always work only with a copy of the data that is anonymized. Assuming the anonymisation step removes / replaces all sensitive data, then whatever the AI agent does, it won't be di
46.
by tudorg 1y ago
On the Xata platform we actually do CoW snapshots and branching at the block device level, which works great. However we are developing pgstream in order to bring in data and sync it from other Postgres providers. pgstream can also do anony
47.
Speeding up PostgreSQL dump/restore snapshots(xata.io)
156 points by tudorg 1y ago|41 comments
48.
by tudorg 1y ago
Answering on behalf of Xata, it is orthogonal. I'm curious to try out Oriole on our platform when I get some time.
49.
From OpenAPI spec to MCP: How we built Xata's MCP server(xata.io)
45 points by tudorg 1y ago|17 comments
50.
by tudorg 1y ago
I think you are describing Xata Agent :) https://github.com/xataio/agent It watches metrics/logs, queries pg_stat_stetements for slow queries, the sends slack notification with suggestions, including indexes, but
51.
by tudorg 1y ago
We use event triggers both in pgroll [0] and pgstream [1] to capture DDL changes. It's a feature of pgroll that it captures the schema migration history, regardless if you do the changes via pgroll or with another tool. And pgstream us
52.
by tudorg 1y ago
[author] Ha, they are actually react-flow, which we use both in the app and on https://xata.io/ For the blog post I actually just used screenshots of the react-flow diagrams, because I was lazy.
53.
by tudorg 1y ago
I would say it's primarily testing: either testing schema changes or testing your application changes. Copy-on-Write branches help because you can spin up an environment fast with relevant data from production (anonymized).
54.
by tudorg 1y ago
There's another thread here: https://news.ycombinator.com/item?id=44016289 Might make sense to merge.
55.
by tudorg 1y ago
[Author here] I'm sorry for the bad experience with Xata. If it's still an issue I'd be glad to have a look. Just to make sure, I suppose this is on the Xata Lite free tier, not on the Postgres at scale platform that this blo
56.
by tudorg 1y ago
You can try with data subsetting tools, a few that I know are: greenmask, jailer, tonic condenser, and I think there are more. They are not exactly for your use case, but might help you a bit. The problem is most of these tools can walk for
57.
by tudorg 1y ago
Yes, exactly, you get a new isolated Postgres database, just started from essentially a snapshot at the time of the fork. You can test any types of changes.
58.
by tudorg 1y ago
We have support for SQL over HTTP in Xata Lite: https://lite.xata.io/docs/sdk/sql/overview
59.
by tudorg 1y ago
1. Yes, we will sign BAA for Pay As You Go. 2. Thanks, I see you sent the email already, not sure why it failed. Will reach out over email.
60.
by tudorg 1y ago
If you want to deploy the whole platform inside your own AWS account, we have a Bring Your Own Cloud model: https://xata.io/byoc If you want to get anonymization from your RDS/Aurora instance and into Xata branches, th

More ›