What do you think of Postgres and Firebird Databases? [closed]

Answer 1

Firebird + FreeadhocUDFs + IBExpert, and just programming.

we have 2 systems in production for 6 years (20 domains, 200 tables, 50 views, 370 stored procedures, 600 triggers, 205 generators, 11, roles, etc, etc) and have been tested to migrate to PostgreSQL (only test, we love Firebird).

In tables with traditional data types (integer, varchar, date, numeric, etc, etc.) differences could be for one or the other, as appropriate, but in stored procedures, Firebird is much more powerful than Postgresql, much more simple and elegant.

Two or three years, any Linux distribution, not including Firebird, only Mysql and Postgresl. Not for nothing today, but tradicionesles distributions (ubunutu / opensuse / fedora / centos, etc, etc) and Firebird include in their repositories.

Postgresql do not say that is worse than Firebird, Firebird is not that much better than Postgresql. But without hesitation I say that Firebird has nothing to envy to Postgresql, and in many ways is more powerful.

(sorry for my bad english)

Answer 2

I love using Postgres - it's powerful, fast, reliable and extremely well documented. The PL/PgSQL language is about as powerful as you could conceivably require, and I can't think of a single serious problem I've ever encountered with it. Most problems tend to be user-created ones, and are resolved after digging through the documentation.

Provided you know a bit about "grown up" databases (i.e. not something like MS Access), or are prepared to learn, I'd wholeheartedly recommend Postgres.

Can't comment on Firebird because I haven't used it

Answer 3

We are using Firebird since 1.0v. It is stable, robust, many features out of the box and extremelly easy to install and mantain.

We develop using .Net and Delphi.

If you choosse FB, fell free to contact us if you need some tips.

Paulo Junqueira.

http://www.rt1.com.br

Answer 4

I've always been impressed with Postgres; it's traditionally had a more complete feature set (in terms of ACID compliance, support for advanced queries, etc.) than MySQL, it has solid Windows ODBC drivers, and its documentation scrupulously points out any areas in which it deviates from the SQL standard. (All databases, it seems, deviate in one respect or another, but Postgres is the only one I've seen that makes sure you know when you're doing so.) I haven't tried the usage scenario you describe, but I've had no problems running it on Linux and accessing it from both Windows ODBC and Linux clients.

I don't have any experience with Firebird; sorry.

Answer 5

I've been working with PostgreSQL, Firebird, Oracle, MySQL, MSSQL more than 6 years ago and my preferred are Firebird and PostgreSQL. I don't like MySQL because Commercial License is not cheap, and MySQL lacks of some functions. I you ask me about what is my preferred one between FB and Pg.... It varies about requirements and needs. I feel that Firebird works better when speed is a must. I've been working with very large databases environments and I have not had problems. PostgreSQL is better in web sites and internet applications developed in PHP, Python and Ruby, but I think that this will not be for much time. In the last months big companies are looking to FB as a very serious DB. I recommend you FB. Try it, give it a chance, you won't be disappointed.

Answer 6

Feature no 1 : Firebird required 0 Administration and is simpler to use than Postgresql (think of sqlite like easy of use with oracle/postgresql like features)

2.Firebird does have Embedded mode and is fully multi threaded in 2.5

3.And yes Firebird is fully multithreaded where Postgresql is NOT

so we are ahead in this area with at least 2 or more years

"All backends running as threads in a single process (not wanted) This eliminates the process protection we get from the current setup. Thread creation is usually the same overhead as process creation on modern systems, so it seems unwise to use a pure threaded model, and MySQL and DB2 have demonstrated that threads introduce as many issues as they solve. Threading specific operations such as I/O, seq scans, and connection management has been discussed and will probably be implemented to enable specific performance features. Moving to a threaded engine would also require halting all other work on PostgreSQL for one to two years."

I will update the post later with more features and links why does http://mapopa.blogspot.com/2010/10/where-firebird-is-better-than.html