Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

This is how long it takes to load data from your Prisma Postgres Postgres DB using Accelerate Stay tuned, video drops tomorrow!

Beto

4,740 subscribers

11,781 views • 1 year ago •via X (Twitter)

Health & Wellness Science & Technology Education

Anya Rossi• Live Now

Private livecam show

0 Comments

No comments available

Comments from the original post will appear here

Related Videos

What Postgres can’t do alone, it can tackle with DuckDB. The pg_duckdb extension shows how two databases can work hand in hand by querying analytical data with DuckDB and joining it with transactional data in Postgres. The extension embeds DuckDB directly into Postgres. DuckDB literally runs inside a Postgres process. How it works (see diagram): 1. An app sends a query to Postgres joining portfolio data (Postgres) with historical market data (lakehouse) 2. pg_duckdb detects lakehouse access and delegates execution to DuckDB 3. DuckDB pulls required market data from the lakehouse, queries Postgres tables, and performs the join 4. Postgres returns the final result to the app

What Postgres can’t do alone, it can tackle with DuckDB. The pg_duckdb extension shows how two databases can work hand in hand by querying analytical data with DuckDB and joining it with transactional data in Postgres. The extension embeds DuckDB directly into Postgres. DuckDB literally runs inside a Postgres process. How it works (see diagram): 1. An app sends a query to Postgres joining portfolio data (Postgres) with historical market data (lakehouse) 2. pg_duckdb detects lakehouse access and delegates execution to DuckDB 3. DuckDB pulls required market data from the lakehouse, queries Postgres tables, and performs the join 4. Postgres returns the final result to the app

Denis Magda

28,678 views • 6 months ago

Need a temporary production-grade Postgres DB to quickly test something? 🚀 Run `npx create-db@latest` and get a connection string, no login needed! Bonus: You can keep the DB beyond 24 hours if you need it, just claim it 😉 👉

Need a temporary production-grade Postgres DB to quickly test something? 🚀 Run `npx create-db@latest` and get a connection string, no login needed! Bonus: You can keep the DB beyond 24 hours if you need it, just claim it 😉 👉

Prisma Postgres

83,514 views • 1 year ago

Real, actual Postgres right from your browser! Learning a lot. This is fun

Real, actual Postgres right from your browser! Learning a lot. This is fun

Aaron Francis

21,237 views • 7 months ago

Insane 1,000 hours of team work we put into this new Neon Postgres home page (Design, Development, Motion). Do you like it? Every single graphic designed fully in Figma. Interactive animations made in Rive. Stay tuned for behind-the-scenes design stories.

Insane 1,000 hours of team work we put into this new Neon Postgres home page (Design, Development, Motion). Do you like it? Every single graphic designed fully in Figma. Interactive animations made in Rive. Stay tuned for behind-the-scenes design stories.

Alex Barashkov

101,789 views • 2 years ago

oh shut up Aaron Francis when you change the website to dark mode it changes the video to dark mode as well what is this dark magic in Mastering Postgres did you build this course platform??

oh shut up Aaron Francis when you change the website to dark mode it changes the video to dark mode as well what is this dark magic in Mastering Postgres did you build this course platform??

Jon Kurtis ⚡

240,237 views • 1 year ago

🎥 New video out! 🤖 Build an AI chatbot Application. We’re going to build a ChatGPT clone completely from scratch. It will have features like conversational context and authentication. Shoutout to Stream and Neon Postgres for making this project happen.

🎥 New video out! 🤖 Build an AI chatbot Application. We’re going to build a ChatGPT clone completely from scratch. It will have features like conversational context and authentication. Shoutout to Stream and Neon Postgres for making this project happen.

Brad Traversy

15,000 views • 1 year ago

A weak password is all it takes for hackers to gain access to your world. Cyber Insurance protects your money, data, and identity, even when mistakes happen. Stay safe. Stay insured.

A weak password is all it takes for hackers to gain access to your world. Cyber Insurance protects your money, data, and identity, even when mistakes happen. Stay safe. Stay insured.

ICICI Lombard GIC

114,010 views • 8 months ago

Starting a new project today, building an end to end system to forecast traffic of flights across cities (starting with Mumbai) The idea is to implement > ingestion service with kafka > data etl with polars > feast for feature store // mlflow for model registry > batch inferencing // dashboard > s3 // postgres for data storage All this orchestrated across multiple DAGs built with Airflow. This year has just been Agents and LLMs all along. Not a bad idea to keep revisiting the traditional format :) Will be posting more of this in the coming days, stay tuned

Starting a new project today, building an end to end system to forecast traffic of flights across cities (starting with Mumbai) The idea is to implement > ingestion service with kafka > data etl with polars > feast for feature store // mlflow for model registry > batch inferencing // dashboard > s3 // postgres for data storage All this orchestrated across multiple DAGs built with Airflow. This year has just been Agents and LLMs all along. Not a bad idea to keep revisiting the traditional format :) Will be posting more of this in the coming days, stay tuned

Aarno

19,481 views • 7 months ago

Big moment for Postgres! Search has always been Postgres' weak spot, and everyone just accepted it. If you needed a real relevance-ranked keyword search, the default answer was to spin up Elasticsearch or add Algolia and deal with the data sync headaches forever. The problem isn't that Postgres can't do text search. It can. But the built-in `ts_rank` function uses a basic term frequency algorithm that doesn't come close to what modern search engines deliver. So teams end up: - Running a separate Elasticsearch cluster just for search - Building sync pipelines that inevitably drift out of consistency - Paying for managed search services that charge per query - Accepting mediocre search relevance because "good enough" ships faster But this is actually a solvable problem. You can realistically bring industry-standard search ranking directly into Postgres, which eliminates the need for external infra entirely. This exact solution is now available with the newly open-sourced pg_textsearch by Tiger Data - Creators of TimescaleDB, a Postgres extension that brings true BM25 relevance ranking into the database. BM25 is the algorithm behind Elasticsearch, Lucene, and most modern search engines. Now it runs natively in Postgres. Here's what pg_textsearch enables: - True BM25 ranking with configurable parameters (the same algorithm powering production search systems) - Simple SQL syntax: `ORDER BY content 'search terms'` - Works with Postgres text search configurations for multiple languages - Pairs naturally with pgvector for hybrid keyword + semantic search That last point matters a lot for RAG apps. The video below shows this in action, and I worked with the team to put this together. You can now do hybrid retrieval (combining keyword matching with vector similarity) in a single database, without stitching together multiple systems. The syntax is clean enough that you can add relevance-ranked search to existing queries in minutes. pg_textsearch is fully open-source under the PostgreSQL license. You can find a link to their GitHub repo in the next tweet.

Big moment for Postgres! Search has always been Postgres' weak spot, and everyone just accepted it. If you needed a real relevance-ranked keyword search, the default answer was to spin up Elasticsearch or add Algolia and deal with the data sync headaches forever. The problem isn't that Postgres can't do text search. It can. But the built-in `ts_rank` function uses a basic term frequency algorithm that doesn't come close to what modern search engines deliver. So teams end up: - Running a separate Elasticsearch cluster just for search - Building sync pipelines that inevitably drift out of consistency - Paying for managed search services that charge per query - Accepting mediocre search relevance because "good enough" ships faster But this is actually a solvable problem. You can realistically bring industry-standard search ranking directly into Postgres, which eliminates the need for external infra entirely. This exact solution is now available with the newly open-sourced pg_textsearch by Tiger Data - Creators of TimescaleDB, a Postgres extension that brings true BM25 relevance ranking into the database. BM25 is the algorithm behind Elasticsearch, Lucene, and most modern search engines. Now it runs natively in Postgres. Here's what pg_textsearch enables: - True BM25 ranking with configurable parameters (the same algorithm powering production search systems) - Simple SQL syntax: `ORDER BY content 'search terms'` - Works with Postgres text search configurations for multiple languages - Pairs naturally with pgvector for hybrid keyword + semantic search That last point matters a lot for RAG apps. The video below shows this in action, and I worked with the team to put this together. You can now do hybrid retrieval (combining keyword matching with vector similarity) in a single database, without stitching together multiple systems. The syntax is clean enough that you can add relevance-ranked search to existing queries in minutes. pg_textsearch is fully open-source under the PostgreSQL license. You can find a link to their GitHub repo in the next tweet.

Akshay 🚀

215,344 views • 6 months ago

This is how anime producers make Parallax! Have you ever tried this? Follow to stay tuned! (aragaogfx)

This is how anime producers make Parallax! Have you ever tried this? Follow to stay tuned! (aragaogfx)

HebertySales

127,278 views • 4 months ago

Talking with someone the other day that estimated they had about 25,000 idle connections to Postgres. My actual response to them: "holy shit". They double checked, it was only about 12,000 Same day had a conversation with someone saying they didn't need pgbouncer because of activerecord's connection pooling. Let's dig into connection pooling in Postgres. Prior to Postgres 14 every connection to the database consumed memory, roughly 10MB, it may be slightly less but it still wasn't free. Even beyond Postgres 14 there is still various contention that happens when Postgres starts to use a connection. An application pooler maintains a set of connections and hands them out when needed on the application side. These are idle and real connections against the database that indeed do impact performance negatively. In contrast pgbouncer speaks the wire protocol, waits for the begin part of the transaction and then uses a connection. It more strictly manages how many idle ones it's having instead of per web server you're running. pgbouncer up until recently really needed to be run in transaction mode (which meant disabling prepared statements in your application framework). prepared_statement support in pgbouncer was added recently, and now you don't have to disable. Even when running with an older version of pgbouncer with prepared_statements disabled you'd still see a big performance gain. A quick check to know if you'd benefit from pgbouncer, run this query: SELECT count(*), state FROM pg_stat_activity GROUP BY 2; If you're idle account is high (yes this is dependent on your view, but to me if it's above 25-30 range, and especially if active is until half that) then you'd already start to benefit from pgbouncer. If it's at 10,000 then post haste get pgbouncer in place. Finally, you don't have to not use a framework pooler, they're fine, but don't think it replaces a native Postgres connection pooler.

Talking with someone the other day that estimated they had about 25,000 idle connections to Postgres. My actual response to them: "holy shit". They double checked, it was only about 12,000 Same day had a conversation with someone saying they didn't need pgbouncer because of activerecord's connection pooling. Let's dig into connection pooling in Postgres. Prior to Postgres 14 every connection to the database consumed memory, roughly 10MB, it may be slightly less but it still wasn't free. Even beyond Postgres 14 there is still various contention that happens when Postgres starts to use a connection. An application pooler maintains a set of connections and hands them out when needed on the application side. These are idle and real connections against the database that indeed do impact performance negatively. In contrast pgbouncer speaks the wire protocol, waits for the begin part of the transaction and then uses a connection. It more strictly manages how many idle ones it's having instead of per web server you're running. pgbouncer up until recently really needed to be run in transaction mode (which meant disabling prepared statements in your application framework). prepared_statement support in pgbouncer was added recently, and now you don't have to disable. Even when running with an older version of pgbouncer with prepared_statements disabled you'd still see a big performance gain. A quick check to know if you'd benefit from pgbouncer, run this query: SELECT count(*), state FROM pg_stat_activity GROUP BY 2; If you're idle account is high (yes this is dependent on your view, but to me if it's above 25-30 range, and especially if active is until half that) then you'd already start to benefit from pgbouncer. If it's at 10,000 then post haste get pgbouncer in place. Finally, you don't have to not use a framework pooler, they're fine, but don't think it replaces a native Postgres connection pooler.

Craig Kerstiens

12,357 views • 1 year ago

This is where it starts, stay tuned to see where this leads on January 14th.

This is where it starts, stay tuned to see where this leads on January 14th.

Ola Electric

504,154 views • 6 months ago

Just finished testing Tesla's FSD with HW4 reacting to a kid darting into the street! Over 20 tests, two days of recording. Check out the teaser below. Full video drops tomorrow—stay tuned!

Just finished testing Tesla's FSD with HW4 reacting to a kid darting into the street! Over 20 tests, two days of recording. Check out the teaser below. Full video drops tomorrow—stay tuned!

Kyle Paul

146,086 views • 1 year ago

Get your skates on: The #StarlightExpress 2024 Cast Recording drops 8 November 2024 AND you can stream the first two tracks from tomorrow 👀 Stay tuned... Pre-Order Full Cast Recording Now | Link in Bio 🛼 #StarlightExpress

Get your skates on: The #StarlightExpress 2024 Cast Recording drops 8 November 2024 AND you can stream the first two tracks from tomorrow 👀 Stay tuned... Pre-Order Full Cast Recording Now | Link in Bio 🛼 #StarlightExpress

Starlight Express

31,857 views • 1 year ago

Oh no, her EBT card is going INACTIVE and she's losing it! 😱 Stay tuned to see how this unfolds! EBTemergency 🛒💳

Oh no, her EBT card is going INACTIVE and she's losing it! 😱 Stay tuned to see how this unfolds! EBTemergency 🛒💳

Dr. CZ

345,562 views • 9 months ago

🚀 My New Book is Here: Data Strategy (3rd Edition) 🚀 I’m thrilled to share the release of my latest bestselling book, Data Strategy: How to Use Data and Artificial Intelligence to Transform Your Business. Every business today needs data to survive - but simply having data is not enough. What matters is how you use it. A well-designed data strategy is the key to unlocking value, driving insights, and giving your organisation the competitive edge it needs to thrive in the digital economy. From small organisations to global enterprises, I’ve seen first-hand how a data-driven approach can transform operations, improve decision-making, and unlock entirely new opportunities. That’s why I’ve poured my experience into this book — to help leaders and teams build strategies that don’t just talk about data, but actually deliver measurable impact. 🔍 In this third edition, I’ve expanded the book to reflect the latest developments in data and AI, including: ✅ Generative AI and its role in shaping business innovation. ✅ Synthetic data and how it can accelerate AI adoption. ✅ The potential of quantum computing and what it means for the future of data. ✅ Expanded guidance on cybersecurity, regulations, and ethics in a data-driven world. This isn’t just a theoretical framework - it’s a practical guide to collecting, managing, and using data effectively in order to drive growth, innovation, and long-term success. Whether you’re leading a start-up or a multinational, Data Strategy will equip you with the tools you need to stay ahead in a rapidly evolving landscape. 📖 Pre-order your copy today: 👉 Amazon - 👉 Kogan Page - I can’t wait to hear how this book helps you craft your own data-driven strategy and transform your business for the future.

🚀 My New Book is Here: Data Strategy (3rd Edition) 🚀 I’m thrilled to share the release of my latest bestselling book, Data Strategy: How to Use Data and Artificial Intelligence to Transform Your Business. Every business today needs data to survive - but simply having data is not enough. What matters is how you use it. A well-designed data strategy is the key to unlocking value, driving insights, and giving your organisation the competitive edge it needs to thrive in the digital economy. From small organisations to global enterprises, I’ve seen first-hand how a data-driven approach can transform operations, improve decision-making, and unlock entirely new opportunities. That’s why I’ve poured my experience into this book — to help leaders and teams build strategies that don’t just talk about data, but actually deliver measurable impact. 🔍 In this third edition, I’ve expanded the book to reflect the latest developments in data and AI, including: ✅ Generative AI and its role in shaping business innovation. ✅ Synthetic data and how it can accelerate AI adoption. ✅ The potential of quantum computing and what it means for the future of data. ✅ Expanded guidance on cybersecurity, regulations, and ethics in a data-driven world. This isn’t just a theoretical framework - it’s a practical guide to collecting, managing, and using data effectively in order to drive growth, innovation, and long-term success. Whether you’re leading a start-up or a multinational, Data Strategy will equip you with the tools you need to stay ahead in a rapidly evolving landscape. 📖 Pre-order your copy today: 👉 Amazon - 👉 Kogan Page - I can’t wait to hear how this book helps you craft your own data-driven strategy and transform your business for the future.

Bernard Marr

10,980 views • 11 months ago

In Web3, data is your edge. For too long, access has been kept away from users. Portal is bringing this power back to the people. With infra that collects the most important on and offchain data - and puts it in your hands.

In Web3, data is your edge. For too long, access has been kept away from users. Portal is bringing this power back to the people. With infra that collects the most important on and offchain data - and puts it in your hands.

Portal

35,555 views • 1 year ago

This is how easy it is to move your BNB from Beacon Chain to BSC (Binance Smart Chain) using #xPortal. Remember, Binance says it’s best to do this before June 2024.

This is how easy it is to move your BNB from Beacon Chain to BSC (Binance Smart Chain) using #xPortal. Remember, Binance says it’s best to do this before June 2024.

xPortal

32,496 views • 2 years ago

Operational databases have long relied on tightly coupled compute and storage. This architecture creates resource contention and pushes teams to manage infrastructure rather than build. As applications become more real time and automated, the transactional layer needs to adapt. Databricks Lakebase is built for that evolution: • Familiar Postgres semantics for app developers • Compute separated from durable state • Operational data running directly on the lakehouse • Serverless autoscaling (including scale to zero), branching, and recovery to match agent-driven workload Now generally available:

Operational databases have long relied on tightly coupled compute and storage. This architecture creates resource contention and pushes teams to manage infrastructure rather than build. As applications become more real time and automated, the transactional layer needs to adapt. Databricks Lakebase is built for that evolution: • Familiar Postgres semantics for app developers • Compute separated from durable state • Operational data running directly on the lakehouse • Serverless autoscaling (including scale to zero), branching, and recovery to match agent-driven workload Now generally available:

Databricks

18,611 views • 5 months ago