Загрузка видео...

Не удалось загрузить видео

На главную

How do Postgres and MySQL achieve data durability? Our very own Chris Sinjakli spoke at SREcon about how this works and the many engineering challenges it presents.

PlanetScale's profile picture

PlanetScale

34,036 subscribers

11,568 просмотров • 7 месяцев назад •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

Комментарии: 0

Нет доступных комментариев

Здесь появятся комментарии из оригинального поста

Похожие видео

Postgres: process-per-connection MySQL: thread-per-connection Learn more about processes, threads, connection pooling, and how they impact database performance in our latest interactive article.
0:34

Postgres: process-per-connection MySQL: thread-per-connection Learn more about processes, threads, connection pooling, and how they impact database performance in our latest interactive article.

PlanetScale

349,333 просмотров • 9 месяцев назад

At scale, you can only put off sharding for so long. YouTube scaled MySQL with Vitess, and now we're building the same for Postgres.
1:29

At scale, you can only put off sharding for so long. YouTube scaled MySQL with Vitess, and now we're building the same for Postgres.

PlanetScale

54,848 просмотров • 1 месяц назад

Sharding is the best way to scale a database. But how does it work? And what's the best way to ensure data and queries are evenly distributed? Our interactive article on database sharding teaches you how.
0:25

Sharding is the best way to scale a database. But how does it work? And what's the best way to ensure data and queries are evenly distributed? Our interactive article on database sharding teaches you how.

PlanetScale

28,639 просмотров • 2 месяцев назад

MySQL vs Postgres: storage engine addition. Clustered indexes (MySQL) and heap tables (Postgres) each have unique advantages. Covered the differences and practical implications in the latest stream.
13:46

MySQL vs Postgres: storage engine addition. Clustered indexes (MySQL) and heap tables (Postgres) each have unique advantages. Covered the differences and practical implications in the latest stream.

Ben Dicken

19,991 просмотров • 1 месяц назад

How Postgres 17 improves IN queries In prior releases, postgres would loop and do multiple "primitive" index scans as many as your IN elements. In Postgres 17 it takes an array and eliminates the need for multiple scans. This only applies for constant values
3:39

How Postgres 17 improves IN queries In prior releases, postgres would loop and do multiple "primitive" index scans as many as your IN elements. In Postgres 17 it takes an array and eliminates the need for multiple scans. This only applies for constant values

Hussein Nasser

143,151 просмотров • 1 год назад

What do we do about the problems government can’t solve? For many Americans, the answer is “roll up our sleeves and take care of it ourselves.” Our new video looks at how everyday citizens are tackling some of the country’s biggest challenges.
7:59

What do we do about the problems government can’t solve? For many Americans, the answer is “roll up our sleeves and take care of it ourselves.” Our new video looks at how everyday citizens are tackling some of the country’s biggest challenges.

Kite & Key Media

441,685 просмотров • 1 год назад

From the archives of our internal Postgres hack week this past spring.
0:56

From the archives of our internal Postgres hack week this past spring.

PlanetScale

15,296 просмотров • 7 месяцев назад

Mayorkas LIED about the screening and vetting of “refugees” from Afghanistan. How many more Rahmanullah Lakanwals are on our soil at this very moment?
1:17

Mayorkas LIED about the screening and vetting of “refugees” from Afghanistan. How many more Rahmanullah Lakanwals are on our soil at this very moment?

I Meme Therefore I Am 🇺🇸

40,376 просмотров • 7 месяцев назад

Whop is building the #1 global creator marketplace. Jack Sharkey, Whop co-founder and CTO, covers how they migrated their 800GB Postgres database to PlanetScale with no downtime and no interruption to site traffic.
2:51

Whop is building the #1 global creator marketplace. Jack Sharkey, Whop co-founder and CTO, covers how they migrated their 800GB Postgres database to PlanetScale with no downtime and no interruption to site traffic.

PlanetScale

19,313 просмотров • 1 год назад

This week at PlanetScale, we lowered the price of your Postgres clusters, shipped new extensions, added support for event triggers, and more 👇
3:01

This week at PlanetScale, we lowered the price of your Postgres clusters, shipped new extensions, added support for event triggers, and more 👇

PlanetScale

33,699 просмотров • 10 месяцев назад

Are processes or threads better for handling connections? Postgres and MySQL make the perfect case-study for this tradeoff.
7:19

Are processes or threads better for handling connections? Postgres and MySQL make the perfect case-study for this tradeoff.

Ben Dicken

14,256 просмотров • 1 месяц назад

PlanetScale + Cloudflare Hyperdrive is perfect for building globally-distributed apps with a high-performance and scalable database. Today we dropped a deep-dive on how this works and why you should use it⬇️
3:23

PlanetScale + Cloudflare Hyperdrive is perfect for building globally-distributed apps with a high-performance and scalable database. Today we dropped a deep-dive on how this works and why you should use it⬇️

PlanetScale

35,513 просмотров • 4 месяцев назад

In all seriousness - how do they engineer these monster machines? How many tries does it take them to make one that actually works? Engineering marvels! 👍
1:01

In all seriousness - how do they engineer these monster machines? How many tries does it take them to make one that actually works? Engineering marvels! 👍

Croxxed Out

15,527 просмотров • 1 год назад

Finish the week with a Postgres video 🌟 All about using JSON in Postgres: - when you should use it - how to use it efficiently - how JSONs actually get stored in postgres.
21:29

Finish the week with a Postgres video 🌟 All about using JSON in Postgres: - when you should use it - how to use it efficiently - how JSONs actually get stored in postgres.

Gwen (Chen) Shapira

27,599 просмотров • 1 год назад

… is, I think, an important new stage in the effort to end democracy as our system of government. Here’s a 3-minute-ish clip of me and Chris Hayes talking (a few weeks ago) about how this was coming and how it works:
3:22

… is, I think, an important new stage in the effort to end democracy as our system of government. Here’s a 3-minute-ish clip of me and Chris Hayes talking (a few weeks ago) about how this was coming and how it works:

Rachel Maddow

266,676 просмотров • 2 лет назад

Aaron Judge and Aaron Boone spoke about how aggressive they want the Yankees to be with their ABS challenges
0:44

Aaron Judge and Aaron Boone spoke about how aggressive they want the Yankees to be with their ABS challenges

Talkin' Yanks

20,714 просмотров • 4 месяцев назад

The volume of this upper body is impressive. I wonder how many years and efforts it took to achieve this😵
0:20

The volume of this upper body is impressive. I wonder how many years and efforts it took to achieve this😵

knockout☆

17,016 просмотров • 7 месяцев назад

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.
0:24

Let Postgres own the Iceberg catalog and delegate analytics to DuckDB. The result => transactional lakehouse updates with fast analytical queries. This isn’t a concept. It’s exactly what pg_lake delivers today. pg_lake combines a set of extensions and components that let you query and modify Iceberg tables (and other lakehouse formats) directly from Postgres. DuckDB is used to accelerate analytical queries and runs in a sidecar process called pgduck_server, which communicates with Postgres during query execution. How it works (diagram below): 1. An application sends a query to Postgres to calculate unrealized PnL (Profit and Loss) for the Disney ticker. 2. Postgres parses the query and identifies the part that computes the average price from historical lakehouse data. 3. That part is forwarded to pgduck_server for accelerated execution. 4. pgduck_server delegates execution to DuckDB, which queries the lakehouse (reusing cached data if available). 5. DuckDB computes the average price and returns it to Postgres. 6. Postgres joins the result with local portfolio data and computes the unrealized PnL. 7. The final result is returned to the application.

Denis Magda

28,473 просмотров • 5 месяцев назад