The Internals of PostgreSQL • Hacker News Board

Re: The Internals of PostgreSQL

#11

Post by datadrivenangel » Mon, Mar 03, 2025, 3:54 PM UTC

rrr_oh_man wrote: post #5

> Transaction logs are an essential part of databases because they ensure that no data is lost even when a system failure occurs. They are a history log of all changes and actions in a database system. This ensures that no data is lost due to failures, such as a power failure or a server crash. The log contains sufficient information about each transaction that has already been executed, so the database server can re…

It's a little clipped, but very straightforward and easy to follow. Not horrendous.

Re: The Internals of PostgreSQL

#12

Post by gpvos » Mon, Mar 03, 2025, 3:54 PM UTC

rrr_oh_man wrote: post #5

> Transaction logs are an essential part of databases because they ensure that no data is lost even when a system failure occurs. They are a history log of all changes and actions in a database system. This ensures that no data is lost due to failures, such as a power failure or a server crash. The log contains sufficient information about each transaction that has already been executed, so the database server can re…

A bit on the wordy side, but better than the average documentation.

Re: The Internals of PostgreSQL

#13

Post by felideon » Mon, Mar 03, 2025, 3:54 PM UTC

nimish wrote: post #9

The worst part of Postgres (and linux) is the awful mailing list driven development process. I have patches to Postgres that I'd rather just keep porting up every version than to try to figure out how to make Outlook work with a 1980s process. The internals themselves are quite nicely engineered as you'd expect

> how to make Outlook work

Well that’s your first problem. Unless you’re using corporate email?

Re: The Internals of PostgreSQL

#14

Post by immibis » Mon, Mar 03, 2025, 4:02 PM UTC

nimish wrote: post #9

The worst part of Postgres (and linux) is the awful mailing list driven development process. I have patches to Postgres that I'd rather just keep porting up every version than to try to figure out how to make Outlook work with a 1980s process. The internals themselves are quite nicely engineered as you'd expect

You are unable to send a message with an attachment? Or what's the problem specifically?

Re: The Internals of PostgreSQL

#15

Post by voctor » Mon, Mar 03, 2025, 4:07 PM UTC

Not related at all but the elephant illustration remind me of the Grand Elephant https://www.lesmachines-nantes.fr/en/discover/the-grand-elep...

Re: The Internals of PostgreSQL

#16

Post by shxx » Mon, Mar 03, 2025, 4:11 PM UTC

paulddraper wrote: post #10

rrr_oh_man wrote: post #5

> Transaction logs are an essential part of databases because they ensure that no data is lost even when a system failure occurs. They are a history log of all changes and actions in a database system. This ensures that no data is lost due to failures, such as a power failure or a server crash. The log contains sufficient information about each transaction that has already been executed, so the database server can re…

What makes the writing horrendous?

If rrr_oh_man's profile is real (https://bit.ly/48d9o9P), his resume appears inconsistent and unprofessional. The emptier a person is, the more likely they are to criticize others.

Re: The Internals of PostgreSQL

#17

Post by nimish » Mon, Mar 03, 2025, 4:18 PM UTC

immibis wrote: post #14

nimish wrote: post #9

The worst part of Postgres (and linux) is the awful mailing list driven development process. I have patches to Postgres that I'd rather just keep porting up every version than to try to figure out how to make Outlook work with a 1980s process. The internals themselves are quite nicely engineered as you'd expect

You are unable to send a message with an attachment? Or what's the problem specifically?

I don't want to waste my time with a process that has zero benefits to me

Re: The Internals of PostgreSQL

#18

Post by nimish » Mon, Mar 03, 2025, 4:19 PM UTC

felideon wrote: post #13

nimish wrote: post #9

The worst part of Postgres (and linux) is the awful mailing list driven development process. I have patches to Postgres that I'd rather just keep porting up every version than to try to figure out how to make Outlook work with a 1980s process. The internals themselves are quite nicely engineered as you'd expect

> how to make Outlook work Well that’s your first problem. Unless you’re using corporate email?

Correct. It's corporate email. Imagine the amount of contributions that are gated behind stupid email policies because some fossil mailing list client can't handle modern email in the year of our lord 2025

Re: The Internals of PostgreSQL

#19

Post by [deleted] » Mon, Mar 03, 2025, 4:29 PM UTC

[deleted]

Re: The Internals of PostgreSQL

#20

Post by [deleted] » Mon, Mar 03, 2025, 4:31 PM UTC

shxx wrote: post #16

paulddraper wrote: post #10

Earlier quoted context omitted.

What makes the writing horrendous?

If rrr_oh_man's profile is real ( https://bit.ly/48d9o9P ), his resume appears inconsistent and unprofessional. The emptier a person is, the more likely they are to criticize others.

[deleted]