caffeinated_me

6 ms·

1.
Postgres Isn't Slow. Your Storage Is(clickhouse.com)
4 points by caffeinated_me 19d ago|0 comments
2.
Pg_stat_ch: Automatic Postgres stat exports to ClickHouse(clickhouse.com)
2 points by caffeinated_me 1mo ago|0 comments
3.
by caffeinated_me 3mo ago
Yeah, I'm probably misremembering some details there. Thanks
4.
by caffeinated_me 3mo ago
Do you have any benchmarks with a mix of long open transactions and short ones? I've struggled a lot with WAL-E in the past there, and am curious if that changes here.
5.
by caffeinated_me 7mo ago
Looks like that still has downtime for a Postgres migration- you're suggesting going into maintenance mode and just doing a dump/restore. I've seen that take hours once you hit the terabyte scale, depending on hardware. I&#x2
6.
by caffeinated_me 8mo ago
Thanks! Out of curiosity, does the NVME have a big effect on replication throughput? I've been wondering how much trouble I've had with other solutions is due to parsing WAL and how much is just slow cloud disk
7.
by caffeinated_me 8mo ago
It sounds like you're doing something similar to how Databricks works now that they've acquired neon, or Snowflake now that they got Crunchy. I'm guessing the local SSD is a big advantage, but what else is different with your
8.
by caffeinated_me 1y ago
I've linked this elsewhere in thread, but here's testing results from a US Navy pilot project for carbon fiber unmanned subs. It looks like this found it pretty viable. https://apps.dtic.mil/sti/pdfs/ADA2
9.
by caffeinated_me 1y ago
This isn't the first carbon fiber submarine, although it is the first manned one. The US Navy tried out an unmanned model in the 80s, and got much better results- they were expecting at least 1000 successful dives before stress fatigue
10.
by caffeinated_me 1y ago
Good find! I've seen similar behavior before and was wondering why it wasn't easy to stop. This isn't the only place Postgres can act like this, though. I've seen similar behavior when a foreign data wrapper times out or
11.
by caffeinated_me 1y ago
I'd argue that horizontally sharded databases can work well, but they do tend to have significant non obvious tradeoffs that can be pretty painful. There's a handful of companies that have scaled Citus past 1PB for production usag
12.
by caffeinated_me 2y ago
It can be great, depending on your schema and planned growth. Questions I'd be asking in your shoes: 1. Does the schema have an obvious column to use for distribution? You'll probably want to fit one of the 2 following cases, but
13.
by caffeinated_me 2y ago
For a multi-tenant use case, yeah, pretty close to thinking about partitioning. For other use cases, there can be big gains from cross-shard queries that you can't really match with partitioning, but that's super use case dependen
14.
by caffeinated_me 2y ago
Depends on your schema, really. The hard part is choosing a distribution key to use for sharding- if you've got something like tenant ID that's in most of your queries and big tables, it's pretty easy, but can be a pain other
15.
by caffeinated_me 2y ago
Seems like this is a similar philosophy, but is missing a bunch of things the Citus coordinator provides. From the article, I'm guessing Citus is better at cross-shard queries, SQL support, central management of workers, keeping schema
16.
by caffeinated_me 2y ago
Any recommendations on telehealth suppliers to contact for that compounded formulation? They're easy to find, but I'm not sure who is trustworthy on this topic.
17.
by caffeinated_me 3y ago
I've generally found something similar- lots of gotchas, but also some very useful products. The best way I've found to approach it is to treat GCP as something that has to be evaluated at an individual service level. It's gr
18.
by caffeinated_me 3y ago
I believe they're referring to the short story of The Road Not Taken, by Turtledove. https://en.wikipedia.org/wiki/The_Road_Not_Taken_(short_stor... PDF of story: https://www.eyeofmidas.com/scifi&#
19.
by caffeinated_me 3y ago
The article mentions a need for primary keys for data sync. Does anyone know if compound primary keys are currently supported? That's been a huge pain for me with the existing stack, so it would be nice to have an alternative.
20.
by caffeinated_me 4y ago
Was that break on Market Street, out of curiosity? After a related incident, I discovered that I was now the 5th co-worker a friend had that had broken a wrist or leg there.
21.
by caffeinated_me 4y ago
We did some trials and ended up on Crunchy Data for the Postgres part of the equation. Wish we had done so earlier, logical replication was a big win. Sadly, we're still using Heroku DNS, but this should accelerate finding an alternati
22.
by caffeinated_me 5y ago
I've seen ZFS being used with Postgres in a few different environments. Seems to work fine for the most part- surprisingly good compression (~8X in one case, usually lower), with the major downside being increased CPU usage when taking
23.
by caffeinated_me 5y ago
My company was seeing GCP Airflow environments not responding, but they seem to have recovered in the past few minutes.
24.
by caffeinated_me 8y ago
This seems to have some fairly scary security implications if used maliciously, but I can't think of a good way to protect against this. Does anyone know of a browser extension to limit access to the history API?