An odd naming decision from an SEO perspective.
Fits right in.
41–50 of 126 posts
An odd naming decision from an SEO perspective.
Fits right in.
> PostgreSQL's query planner/optimizer is decidedly state-of-the-art Postgres's cost-based planner is good, but it's a decidedly 1980s design, predating the famous but also outdated Volcano/Cascades systems (used by Microsoft SQL Server and CockroachDB and others). So much has happened in the field of query optimization in the last 30 years, very little of which has ended up in Postgres, I think. Postgres has gotten…
If I am scraping giant amounts of data I would run far away from Postgres for other databases like Amazon Redshift.
Postgres is great, but the level of work required to scale it on large workloads is really quite overwhelming. You really need expert-level knowledge to scale it. Just ask anybody who has had to shard their database.
The DBA was having fun with my silly idea until Slow-Query takes 10 seconds and we flipped back over to the production systems with much more allowed memory for postgres.
My purpose was to show that Linux itself is pretty fast at caching and paging, even if Postgres was hamstrung. The db actually ran fine except for the slow queries, and we probably could have cleaned them up, too. But I proved my point.
DB was ~300GB, metal had 512GB RAM. This was in 2012.
Co-founder here - AMA.
[0] https://en.wikipedia.org/wiki/Temporal_database
[1] https://github.com/scalegenius/pg_bitemporal/blob/master/doc...
Co-founder here - AMA.
> PostgreSQL's query planner/optimizer is decidedly state-of-the-art Postgres's cost-based planner is good, but it's a decidedly 1980s design, predating the famous but also outdated Volcano/Cascades systems (used by Microsoft SQL Server and CockroachDB and others). So much has happened in the field of query optimization in the last 30 years, very little of which has ended up in Postgres, I think. Postgres has gotten…
Guess I'll keep using Postgres.
GCP has very cool high availability, backup and monitoring features that I’d hate to loose if we move to their cloud offering. Can you configure which region your data is in? Can you put it behind / inside a VPC?
Couldn’t really find that info in the docs / pricing pages.
Postgres is great, but the level of work required to scale it on large workloads is really quite overwhelming. You really need expert-level knowledge to scale it. Just ask anybody who has had to shard their database.
I ran a 4000qps postgres database set to use no more than 640KB of RAM (its in the configs). The DBA was having fun with my silly idea until Slow-Query takes 10 seconds and we flipped back over to the production systems with much more allowed memory for postgres. My purpose was to show that Linux itself is pretty fast at caching and paging, even if Postgres was hamstrung. The db actually ran fine except for the slow…