41–50 of 61 posts
Earlier quoted context omitted.
Would such approach work for MS SQL?
There's no reason why it shouldn't, Delphix primarily targeted Oracle, but there is of course not as much open-source enthusiasm for supporting a proprietary database as an open-source one.
If you use xfs (+`file_copy_method=CLONE`) you can do this with Postgres 18. `CREATE DATABASE clankerdb TEMPLATE sourcedb STRATEGY=FILE_COPY;`. But Ardent can be useful for many, because cloud providers uses heavily restricted Postgres. And many use Aurora, which doesn't event let configure the `log_line_prefix`. Though if cloud providers add file_copy_method=CLONE compatible managed pg ... ref: https://boringsql.com…
I wanted to try doing something similar to this in our dev environment (think shared dev database but per branch clones), but this limitation seemed tricky to accept: > The source database can't have any active connections during cloning. I wouldn't mind some lock contention, but having to kill all connections seemed a bit harsh
So you don't need to touch real production db?
Not sure if it applies for all use cases tou
Does it clone the data? We have a table with 35GB data, what happen in that case?
Does it clone the data? We have a table with 35GB data, what happen in that case?
Their website says they clone at 6s/TB so you probably will get a branch less than 1s
``` CREATE DATABASE cloned_db WITH TEMPLATE source_db OWNER your_owner; ```
[flagged]
LLMs are amazing and we use them heavily ourselves - but not for modifying text that is to be posted to HN. Doing so leaves imprints on the language that readers are increasingly allergic to, and we want HN to be a place human conversation.
“Never impacts production data” is impossible to guarantee. Playing with real world data often has side effects outside of the database. For example if you store oauth tokens to external services in your DB (customer integrations) it’s easy to mess up your customers data through a bad API call (been there done that). There is still value in carefully testing on your prod DB, but for that you could just easily maintai…
[flagged]
LLMs are amazing and we use them heavily ourselves - but not for modifying text that is to be posted to HN. Doing so leaves imprints on the language that readers are increasingly allergic to, and we want HN to be a place human conversation.
“Never impacts production data” is impossible to guarantee. Playing with real world data often has side effects outside of the database. For example if you store oauth tokens to external services in your DB (customer integrations) it’s easy to mess up your customers data through a bad API call (been there done that). There is still value in carefully testing on your prod DB, but for that you could just easily maintai…
If it’s production data I probably don’t trust a random startup with it. I’m very confused as to the target market here
How do you get a staging and dev db together that’s going to let you test your migrations?
What Ardent does makes sense for a team setting where several agents/developers require their own environment before deploying code. But from a one-man-show founder’s perspective, the constraint is not about isolation but rather self-discipline.