Exercise 1: The Governance/Ownership Difference and Its Practical Consequence — Possible Solution
====================================================================

THE GOVERNANCE/OWNERSHIP DIFFERENCE
------------------------------
Per this chapter, "MySQL began as MySQL AB, was acquired by Sun
Microsystems in 2008, and then by Oracle in 2010 — it's now owned
outright by a single corporation, dual-licensed under the GPL and a
commercial license." PostgreSQL, by contrast, "is now developed by
the PostgreSQL Global Development Group — a community-driven
governance model with no single owning company, released under the
permissive, MIT/BSD-style PostgreSQL License."

The core difference is ownership structure: MySQL answers, ultimately,
to a single corporation (Oracle) that controls its licensing and
roadmap; PostgreSQL answers to a decentralized community of
contributors and committers, with no company able to unilaterally
change its licensing terms.

ONE CONCRETE PRACTICAL CONSEQUENCE
------------------------------
Per this chapter, "there's no dual-licensing tension to navigate with
Postgres, no single vendor who could change licensing terms or
direction unilaterally, and new features land based on community and
committer consensus rather than one company's own product roadmap."

A concrete example: an organization building a commercial product on
MySQL has to be aware of MySQL's dual-licensing model — depending on
how the product is distributed, it may need to comply with the GPL or
instead purchase a commercial license from Oracle. With PostgreSQL,
this specific licensing consideration simply doesn't exist in the
same way, since its permissive license doesn't create that same
GPL-vs-commercial fork in the road for downstream users. This is a
genuine, practical business/legal consequence that traces directly
back to the different ownership structures the chapter describes.

WHY THIS WORKS AS AN ANSWER
------------------------------
It identifies the specific structural difference (single corporate
owner vs. decentralized community governance) using the chapter's own
wording, and traces it to a concrete, real-world licensing
consequence rather than a vague "one is more open than the other"
claim.