G2

Pramoda H.

Full Stack Developer

Program Development

Small-Business (50 or fewer emp.)

5/25/2026

"Solid relational database for a real-world PHP clinic management system"

4.5/5

What do you like best about PostgreSQL?

I use PostgreSQL as the core database for a Pet Clinic Management System I built. It supports multi-role authentication (admin, doctor, staff, and pet owners), appointment scheduling, medical records, vaccination tracking, and invoice management, all within a single relational schema.

What I value most is PostgreSQL’s ability to enforce complex relational integrity. In my system, the appointments table includes foreign key constraints that link to animals, owners, doctors, schedules, and staff at the same time. PostgreSQL handles cascading deletes and referential integrity smoothly—for instance, when an owner is deleted, their associated animals and related records are automatically removed.

I also like the strong support for enum types, sensible timestamp defaults, and multi-column unique constraints, such as preventing duplicate owner registrations. These features made my schema design cleaner and more dependable. On the application side, PostgreSQL integrates well with PHP via PDO, so parameterized queries are easy to write and help keep the system secure against SQL injection. Review collected by and hosted on G2.com.

What do you dislike about PostgreSQL?

Initial setup and configuration—especially when it comes to user roles, privileges, and connection pooling—feels more involved than with simpler databases. In my case, for a pet clinic system I run locally using XAMPP/MariaDB syntax, migrating the schema to PostgreSQL took extra care because of syntax differences (for example, AUTO_INCREMENT vs. SERIAL and how enums are handled).

On top of that, debugging complex multi-join queries—such as joining appointments with animals, owners, doctors, and schedules—can lead to error messages that are difficult to interpret, particularly for developers coming from a MySQL/MariaDB background. Review collected by and hosted on G2.com.

What problems is PostgreSQL solving and how is that benefiting you?

My pet clinic system manages eight interrelated tables—admins, owners, animals, doctors, staff, appointments, medical records, vaccinations, and invoices. PostgreSQL keeps this data consistent through foreign key constraints and transactional integrity, which is especially important when booking appointments or updating medical records.

For instance, when I create an appointment, the record needs to validate several things at once: that the animal exists, the owner matches that animal, the doctor is active, and an appropriate time slot is available. PostgreSQL’s transaction support also means there are no partial writes if any part of that process fails.

As a result, I’ve eliminated data integrity bugs in my application and cut down on the amount of validation logic I have to write in PHP, since the database enforces consistency at the schema level. Overall, it’s made the system more reliable and easier to maintain as I continue adding features. Review collected by and hosted on G2.com.