Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I don't know PostqreSql. In fact I've never heard the name before. But what would you like to do with it? I can recommend Interbase. It's free and was awarded 2nd place (after Oracle) for the best database.
Sorry the name of the second SQL is PostgrelSql or something like that (I haven't the name in front of me).
Please if anyone has seen any of the above, I would appriciate his(her) opinion about them
Distribution: Debian, Red Hat, Slackware, Fedora, Ubuntu
Posts: 13,602
Rep:
I would like to reiterate what was already said. Both are VERY good. As you may know this site uses MySQL.
PostgreSQL is mostly SQL92 compliant. It has views, is ACID compliant and has triggers. It is VERY fast on selects, but because of the way it indexes is a little slower on INSERTS. It seems to be a little more resource intense and is a little harder to learn.
MySQL is just now starting to support things like transactions (You need a special table type - InnoDB) but is much easier to learn/install/tweak in my opinion. It is super fast but will not scale as well.
So really, as in most cases, neither are better - they both have their strengths and weaknesses.
I've found that unfortunately, the backend listener in postgres is easily broken!
Postgres lasted about 4 days of intensive use before the backend started complaining, shutting down mid-request and requiring the postmaster to be restarted before every use.
Rebuilding doesn't work either, so I'm going to try MySQL next.
These things are set to test us.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.