The discussion around selective async commits in PostgreSQL centers on the trade-offs between durability and performance. Selective async commits allow certain transactions to be acknowledged before they are completely written to disk, which can enhance performance but at the risk of compromising the strict transaction guarantees of ACID compliance. User comments highlight concerns over this feature, particularly its potential to break transaction guarantees in critical applications, while suggesting that it might find utility in scenarios like logging where performance is prioritized. This indicates a crucial consideration for developers when deciding whether to implement selective async commits based on the specific requirements of their applications. The balancing act between durability and performance is an ongoing challenge for database management.