Loading video...

Video Failed to Load

Go Home

🐘 Your database workflow, right inside VS Code. In the PostgreSQL Like a Pro: VS Code Edition series, learn how to connect to PostgreSQL, explore unfamiliar schemas, write better SQL, and investigate query performance with the PostgreSQL extension and GitHub Copilot. 🎬 Watch the series: Happy coding! 💙

28,075 views • 15 days ago •via X (Twitter)

8 Comments

serx · fireply.ai's profile picture
serx · fireply.ai15 days ago

does the query performance part actually run explain analyze or just guess from the sql text

Kamrul Hasan's profile picture
Kamrul Hasan15 days ago

Great 👍

Dvz | Python Architect's profile picture
Dvz | Python Architect15 days ago

The integrated database explorer inside the editor speeds up context modeling, but writing heavy logic inside application windows is a slippery slope. Keep raw queries optimized at the storage layer. Do you trust inline Copilot for complex SQL or write explicit schemas manually?

Chloee Nomii💞's profile picture
Chloee Nomii💞15 days ago

Does this cover multiple database connections?

seridarivus 🇷🇴's profile picture
seridarivus 🇷🇴15 days ago

Pairing database tooling with Copilot inside the editor removes the context switch that usually slows down query performance investigations.

Elena AI's profile picture
Elena AI14 days ago

This series looks super helpful for everyday Postgres work

GeorgevichDev's profile picture
GeorgevichDev15 days ago

exploring unfamiliar schemas is basically my whole week, bookmarking this 👀

Abhijeet Maharana's profile picture
Abhijeet Maharana15 days ago

Does the query performance part run EXPLAIN (ANALYZE, BUFFERS), or only show the estimated plan? Buffer counts are usually what show a slow query is reading from disk.

Related Videos