Database Administrators Stack Exchange is a question and answer site for database professionals who wish to improve their database skills and learn from others in the community. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I read that MySQL has binary safe blobs, but PostgreSQL does not.

So far what I've found suggests that "binary safe" is something that really relates to functions and handling of data, not the data itself. It seems that the difference is that MySQL natively has ways of storing and manipulating blobs without having to specify data formatting, but PostgreSQL requires using either "quoted-printable encodings" or "base64" encoding for binary data.

Is that all there is to it? What else should I worry about with respect to the differences between MySQL and PostgreSQL in the handling of blobs? I'm starting a new project, not migrating data, so I'm just wondering if there are particular reasons to choose one or the other with respect to their handling of binary blobs.

share|improve this question
up vote 4 down vote accepted

That reference you link to is complete nonsense. PostgreSQL supports binary data and binary-safe handling of data just fine.

There will be some small differences between MySQL and PostgreSQL about how the types and certain functions are named, but overall it won't make much difference. There are probably other, better reasons for choosing one system over the other.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.