Sometimes, developers may take easy paths while designing a schema. This is where the developers unknowingly get into the world of complex workarounds. For example, a "SELECT FOR UPDATE" to lock a row for each transaction, compared to the planning upfront in using Advisory locks in PostgreSQL. One of the famous issues is related to integers reaching its limits. This is where the data type has to be altered to a bigint to avoid potential impact. This is where, as a DBA, it is important to show metrics of how the integers are being consumed and what you estimate as the time before it is out of its range.Proving through performance benchmarks, past statistics and relevant data points, can always convince developers in approving schema changes.

To navigate conflict over database schema changes with developers: 1. Communicate Early: Involve developers in discussions about schema changes from the start to address concerns proactively. 2. Explain the Why: Clearly articulate the reasons for the changes, focusing on how they benefit performance, scalability, or usability. 3. Provide Testing Environments: Offer safe testing environments where developers can evaluate the impact of changes without risking production. 4. Collaborate on Solutions: Seek input from developers to co-create solutions that balance both database and application needs. 5. Adopt Change Management: Use formal processes and tools to document, review, and approve changes collaboratively.