Apart from the usual advice to "start working on a patch to learn the internals," which is not as easy to do because it's a mature product and most of the low-hanging fruits have been reaped, I'd also suggest checking the extensions shipped with the main source tree under $top/contrib.
Each one is self-contained and usually works with a subset of the internals.
Some good ones: pageinspect, pg_buffercache, pg_prewarm, pg_statstatements, pg_walinspect
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
Parent probably means that email clients don't send the attachments (patches) with the appropriate content type (i.e. text/x-patch or text/x-diff) but use application/octet-stream.
> 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 recover the database cluster by replaying the changes and actions in the transaction log in the event of a server crash.
How would you rephrase it? I'm also a non-native English speaker, and the bit you provided sounds very easy to understand because of how it's phrased. There are minor redundancies, but that's all I noticed...
[+] [-] brasetvik|1 year ago|reply
[+] [-] voctor|1 year ago|reply
[+] [-] fforflo|1 year ago|reply
[+] [-] HackerThemAll|1 year ago|reply
[+] [-] codepathfinder|1 year ago|reply
[+] [-] topherjaynes|1 year ago|reply
[+] [-] nimish|1 year ago|reply
The internals themselves are quite nicely engineered as you'd expect
[+] [-] immibis|1 year ago|reply
[+] [-] felideon|1 year ago|reply
Well that’s your first problem. Unless you’re using corporate email?
[+] [-] fforflo|1 year ago|reply
[+] [-] tracker1|1 year ago|reply
[+] [-] unknown|1 year ago|reply
[deleted]
[+] [-] rrr_oh_man|1 year ago|reply
The writing is horrendous
[+] [-] tasuki|1 year ago|reply
[+] [-] datadrivenangel|1 year ago|reply
[+] [-] skotobaza|1 year ago|reply
[+] [-] paulddraper|1 year ago|reply
[+] [-] gpvos|1 year ago|reply