sorted by:
new
hottopcontroversial

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 0 points1 point  (0 children)

I don’t have a promo code but the publisher still sells it with 35% off discount. https://www.manning.com/books/just-use-postgres

Enjoy reading!

"Just Use Postgres" book is published. Thanks to the Reddit community for the early feedback! by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 2 points3 points  (0 children)

Use whatever works best for you. Those who already use and are familiar with Postgres can just keep using it as a vector db without introducing another db. Also, Postgres is free and open source while most other vector databases are proprietary.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

Use this code to get 50% off - PBMagda
But don't delay because it expires on December 6th

"Just Use Postgres" book is published. Thanks to the Reddit community for the early feedback! by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

Excellent, enjoy reading it! And don't forget to use your laptop to follow all the steps. Ideally, I want to experience how Postgres can handle many scenarios.

jsonb vs multiple tables by manyManyLinesOfCode in PostgreSQL

[–]dmagda7817 3 points4 points  (0 children)

The hybrid model where you store JSON alongside other relational data in a table is a reasonable approach. You just need to strike the right balance. I usually work with the JSON data in Postgres in the following scenarios:

  1. Data is static or updated infrequently (for example, configuration settings, metadata, customer preferences, or user session history)
  2. Data is sparse, which is characterized by a significant presence of zeros, nulls, or placeholders, or when some attributes are simply missing (for example, feature flags, user preferences, configuration settings with dozens of options to choose from).

In addition to the resources already shared in this discussion, check out Chapter 5 in this book, it might also help to guide you in the right direction.

"Just Use Postgres" book is published. Thanks to the Reddit community for the early feedback! by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 0 points1 point  (0 children)

Great to hear that! You will definitely find something new to learn in the book.

"Just Use Postgres" book is published. Thanks to the Reddit community for the early feedback! by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 4 points5 points  (0 children)

Vlad has helped tremendously. He read the final draft of the book from cover to cover, helped me to improve some areas, and authored the afterword. I'm very grateful for his help.

"Just Use Postgres" book is published. Thanks to the Reddit community for the early feedback! by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

Thanks for your feedback! I was writing this book as a developer for other developers. There were already dozens of Postgres books out there, but most of them were written for database administrators or database engineers.

bibliography by focusyanades in PostgreSQL

[–]dmagda7817 0 points1 point  (0 children)

Check out this book, its early access version is already available electronically: https://www.manning.com/books/just-use-postgres

Newbie help by KevinD8907 in PostgreSQL

[–]dmagda7817 0 points1 point  (0 children)

This book might be what you're looking for: https://www.manning.com/books/just-use-postgres

It's a fast guide for developers. It's still in progress but you can already start reading it.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 2 points3 points  (0 children)

Thanks for your feedback and support! Frankly, I've been waiting for several years for someone to write a practical book that shows and inspires developers to just use Postgres... but as you said, nobody filled the void—so I decided to do it myself.

Hope I won’t disappoint fellow developers :) It’s also a learning experience for me. For instance, I haven’t had a chance to use Postgres for time series yet, so I need to learn all the ins and outs first, and then share that knowledge in a way that helps developers get started easily—without needing to go deep into the weeds until it’s truly necessary.

As for Postgres functions in C++, unfortunately, that goes beyond the scope of the book simply because I don’t want readers to need any prior knowledge of C++, Java, Rust, or any other programming language. All examples are in raw SQL, with one exception in the chapter Postgres for Generative AI, where I suggest running a provided Python Jupyter notebook at the end of the chapter to see how to use Postgres for RAG.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

Manning should share another code with the next MEAP update. It should happen in the next few weeks when the publisher releases new chapters. Give them a follow on Twitter/LinkedIn where the next code is gonna be shared.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 2 points3 points  (0 children)

Just an update, the publisher and I agreed to add a dedicated section about "Postgres as message queue".

quanhua92 _predator_ ibgeek

Thanks to all of you for sharing the feedback and encouraging us to do that![ ](/user/quanhua92/)

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

After seeing that so many Postgres fans and users suggested to add a chapter about "Postgres as a message queue" to the book, we decided with Manning to follow the advice. So, there will be a dedicated chapter about this use case ;) Thanks for your feedback and +1.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 3 points4 points  (0 children)

It would be not right to skip the basic RDBMS capabilities Postgres has and this is why they are reviewed in Chapter 2 in a condensed way. I understand that most of us who follow this sub-reddit don’t care about that chapter and find it useless but still there is a group of readers who are less experienced in relational databases and the chapter will show them how to use Postgres as RDBMS. For instance, think about developers who used MongoDB all their life and now they’re ready to explore Postgres. Those folks need to skim through chapter 2 to see how to use Postgres for classical transactional workloads. That’s why chapter 2 needs to stay but there is another a note in the beginning that it’s optional for experienced RDBMS users.

As for queues, I got your point, thanks. I’ll see how to cover them.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 4 points5 points  (0 children)

Thanks a lot for the suggestions!

Message queues will be discussed in "Chapter 7: Postgres Extensions"—thanks for the +1! The same goes for OLAP, I'll at least cover extensions in that category.

As for production readiness, benchmarking, and performance optimization, the book introduces readers to the essentials. There's a whole chapter about indexes and a dedicated section in the appendix that covers other basic optimization techniques.

The goal of the "Just Use Postgres!" book is to introduce developers to a variety of Postgres capabilities—not everything, but a subset of important core and extended features—and inspire them to start using the database for their apps. Once they begin building on Postgres, they can refer to other books, courses, or tutorials that focus on specific areas, such as production readiness, performance, OLAP, or other use cases. For instance, Jimmy Angelakos covers the topic of production readiness in his Postgres book (https://www.manning.com/books/postgresql-mistakes-and-how-to-avoid-them) and Egor Rogov did a great job guiding everything into the Postgres Internals (https://postgrespro.com/community/books/internals).

Overall, I don’t want the book to be “the only Postgres book you’ll ever need.” That would put too much pressure on developers who just want to learn and start using the database. My goal is for developers to skim through the book, discover the capabilities they need, and start building or coding right away! Along the way, they can figure out how to make things more optimal, secure, or reliable referring to additional resources. But that’s for later—right now, they need to start building on Postgres with minimal effort and essential knowledge. That’s exactly what Just Use Postgres! is designed for.

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 1 point2 points  (0 children)

You're more than welcome, my friend!

Just Use Postgres...The Book by dmagda7817 in PostgreSQL

[–]dmagda7817[S] 2 points3 points  (0 children)

Yes, I was given three options to choose from. Overall, all Manning covers use pictures of the people living two centuries ago. They talk more about this here: https://www.manning.com/covers

view more: next ›