Technically yes, but they're used interchangeably nowdays. Plus, the official transcript mentions "Mytilene" so I wanted to follow that. Although I use Lesvos myself.
In 2021, during a visit to the Greek island of Mytilene, Pope Francis delivered one of the finest speeches I've ever read:
> This great basin of water, the cradle of so many civilizations, now looks like a mirror of death. Let us not let our sea (mare nostrum) be transformed into a desolate sea of death (mare mortuum). Let us not allow this place of encounter to become a theatre of conflict. Let us not permit this “sea of memories” to be transformed into a “sea of forgetfulness”. Please brothers and sisters, let us stop this shipwreck of civilization!
> We are in the age of walls and barbed wire. To be sure, we can appreciate people’s fears and insecurities, the difficulties and dangers involved, and the general sense of fatigue and frustration, exacerbated by the economic and pandemic crises. Yet problems are not resolved and coexistence improved by building walls higher, but by joining forces to care for others according to the concrete possibilities of each and in respect for the law, always giving primacy to the inalienable value of the life of every human being
spat is a Redis-like in-memory data structure server embedded in Postgres. Data is stored in Postgres shared memory. The data model is key-value. Keys are strings, but values can be strings, lists, sets, or hashes.
I tend to agree. The OOP-all-the-things mantra created many problems; lots of books were printed (more than necessary), and lots of evangelists made their name on unnecessary abstractions over abstractions.
One might blame Java for that, but it's a chicken-and-egg problem.
Whenever I read something about Boston Dynamics now, I can't help but remember that scene from Silicon Valley (HBO) where Eric kicks BigDog https://www.youtube.com/watch?v=BFnMBW95RZI
PostgreSQL 18 won't have many JSON enhancements - how much better can it get after all?
And virtual generated columns will probably be the highlight of the release.
But there's always some room for improvement. One long-standing pain point has been simply removing nulls from JSON arrays.
Of course, there are, but I guess this relies on the various System views (pg_*), like most monitoring tools, which have fine-grained control access if you create appropriate roles.
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
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.
tselai.com