free-gophers-pack VS pgadmin4

Gopher credits

OK, no more surprises. I promised with that, we now have a full understanding of the main ideas, both big and sneaky, behind the Go scheduler. We started out with a list of goals. How did we do with our goals? Use a small number of kernel threads. We can support high concurrency and we can leverage parallelism. We scale to N-cores and this falls out of those three ideas that we discussed. Let's move on to the harder questions. What are the limitations of the scheduler? Well, for one, there is no notion of goroutine's priority. It uses a first in, first out runQueue vs Linux scheduler which uses a priority queue. Now the cost-benefit tradeoff is doing this might not actually make sense for go programs. The second limitation is there's no strong preemption, so there is no strong fairness in latency guarantees. It's entirely possible for a goroutine in certain cases to bring the inspire system to slow down in a fault. And finally, the third limitation that I want to touch upon today is the scheduler is not aware of the actual hardware topology, so there's no real guaranteed locality between the data and the Goroutine computation, and with that we have come to an end and thank you for reading. Gopher Artwork credit Maria Letta Ashley Mcnamara

I used the Gophers from here - https://github.com/MariaLetta/free-gophers-pack/ and did give a credit to the author in the video and put a link in the description

If we access a client like PgAdmin or Beekeeper, or accessing its container via bash and checking via CLI, we can see that the table was created successfully:

You can install pgAdmin on Windows and connect the GUI Admin/developer tool directly to your PostgreSQL server running in WSL.

With this tool, deciphering the details of PostgreSQL query plans becomes a little more approachable. Just be mindful that using it involves sharing your query and its plan publicly. If privacy is a concern regarding sharing your query and its plan publicly, consider using pgAdmin, an open-source administrative tool for PostgreSQL that you can install on your local machine, which also offers a visualization feature for query plans.

This isn’t meant to be an exhaustive list. There are many other database management software packages out there, including MySQL Workbench, DBeaver, and pgAdmin. We’ve chosen these database tools because they cover the most common database systems and use cases, but if you find they aren’t meeting your needs, be sure to explore further or consider building your own database user interface — it’s easier than you think.

pgAdmin to PostgreSQL is what phpMyAdmin is to MySQL, and it can be used on Linux, Unix, macOS and Windows to manage PostgreSQL. pgAdmin 4, the latest pgAdmin, is a complete rewrite of pgAdmin using Python and Javascript/jQuery.

I've attached my full crash report. Please, HALP! I don't want to keep using DBeaver! crashreport-jont.pdf