Live data from Hacker News

EdgeDB is now Gel and Postgres is the future

geldata.com

21–30 of 126 posts

Re: EdgeDB is now Gel and Postgres is the future

#21
post #3

Co-founder here - AMA.

How to deal with eventual slow queries? I currently have a system with complex queries with a lot of joins where I had to create a custom materialized table

These queries also deal with permissions & realtime scheduling so endpoint caching doesn't solve it

Have gel users hit any performance issues, and how have they dealt with them?

Re: EdgeDB is now Gel and Postgres is the future

#22
Just wish the local development story wasn't so bound to a installation or the concept of instances. I just want a compose file in my repositories that starts Postgres and "Gel" separately with the option to execute commands within the container

I mean, I don't need it anymore because I did it myself now, but it definitely annoys me that it's not first class

Re: EdgeDB is now Gel and Postgres is the future

#23

> 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…

How does MySQL compare? I get the sense that innovations land there sooner because of all the mega corps that use it.

Re: EdgeDB is now Gel and Postgres is the future

#24

Just wish the local development story wasn't so bound to a installation or the concept of instances. I just want a compose file in my repositories that starts Postgres and "Gel" separately with the option to execute commands within the container I mean, I don't need it anymore because I did it myself now, but it definitely annoys me that it's not first class

Btw, I want to start them separately because we deploy a standard HA Postgres cluster and want to rely on proven tooling.

Re: EdgeDB is now Gel and Postgres is the future

#25

Just wish the local development story wasn't so bound to a installation or the concept of instances. I just want a compose file in my repositories that starts Postgres and "Gel" separately with the option to execute commands within the container I mean, I don't need it anymore because I did it myself now, but it definitely annoys me that it's not first class

You can use Docker (and Docker Compose) with Gel for local development [1], but of course you'd miss out on most management features of the CLI, because it's not built to supplant the docker/docker-compose CLI. Are there any particular issues you have currently with the Docker image approach?

[1] https://docs.geldata.com/resources/guides/deployment/docker

Re: EdgeDB is now Gel and Postgres is the future

#26

Just wish the local development story wasn't so bound to a installation or the concept of instances. I just want a compose file in my repositories that starts Postgres and "Gel" separately with the option to execute commands within the container I mean, I don't need it anymore because I did it myself now, but it definitely annoys me that it's not first class

Btw, I want to start them separately because we deploy a standard HA Postgres cluster and want to rely on proven tooling.

That's already supported, you just need to set the Postgres cluster URI in the `GEL_SERVER_BACKEND_DSN` env var ([1]).

[1] https://docs.geldata.com/reference/reference/environment#gel...

Re: EdgeDB is now Gel and Postgres is the future

#27
post #21
post #3

Co-founder here - AMA.

How to deal with eventual slow queries? I currently have a system with complex queries with a lot of joins where I had to create a custom materialized table These queries also deal with permissions & realtime scheduling so endpoint caching doesn't solve it Have gel users hit any performance issues, and how have they dealt with them?

We're shipping a slow query log UI in this version to continuously monitor queries in your system.

Our users do get performance issues, usually because they start really using our data model to its full potential, creating tens / hundreds complex access policies, 100-lines long EdgeQL queries etc. We have EXPLAIN command to deal with, and we also support our customers directly helping them understand and fix their system. All of the findings trickle down to the core product so that the rest can benefit too.

Re: EdgeDB is now Gel and Postgres is the future

#28

> 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…

The paper seems to mostly focus on the quality of cardinality estimation (mostly driven by statistics) which is admittedly one of the frequent sore points in Postgres. There's been some progress in that area though (CREATE STATISTICS being a highlight).
Post reply on HN