Internals of Go 1.24's New Garbage Collector and How It Reduces Latency vs. Java 21

Author

ANKUSH CHOUDHARY JOHAL

@johalputt

Stats

Reactions0

Comments0

Read Time0 min

Published

JoongHyuk Shin3d ago • 6 min read

1.1.3 Optimizable vs Utility

Inside the five-stage pipeline from 1.1.1, there is another fork right after the parser. PostgreSQL....

#postgres#database#internals#sql

2 2

JoongHyuk Shin3d ago • 8 min read

1.1.2 Simple vs Extended

The fork visible in 1.1.1 — simple query protocol on one side, extended on the other — is the subjec...

#postgres#database#internals#protocol

1 0

JoongHyuk Shin3d ago • 9 min read

1.2.1 From SQL Text to Raw Parse Tree

A line like SELECT name FROM users WHERE id = 1 arrives at the backend. As we saw in 1.1.1, the...

#postgres#database#internals#parser

0 1

1.2.2 Semantic analysis: name resolution, type checking, catalog lookup

JoongHyuk Shin1d ago • 10 min read

1.2.2 Semantic analysis: name resolution, type checking, catalog lookup

A raw parse tree captures the structure of SQL text, but not what that structure refers to. Whether....

#postgres#database#internals#sql

0 1

JoongHyuk Shin4d ago • 5 min read

1.1.1 Life of a Query

PostgreSQL Internals · Chapter 1 Query Processing · 1.1 Where Does a Query Go? This section is the....

#postgres#database#internals#protocol

1 0

JoongHyuk Shin4d ago • 1 min read

1.1 Where Does a Query Go?

PostgreSQL Internals · Chapter 1 Query Processing Suppose a client sends SELECT * FROM users WHERE....

#postgres#database#internals#backend

1 0