The new PostgreSQL version, 7.4, includes a host of new features which make PostgreSQL a more powerful and scalable database for large enterprises. These include AMD Opteron optimization, improved index maintenance tools, and enhanced support of full text indexing which adds ranked result sets. Combined with the recent contribution of the eRServer replication solution, these advances fulfill PostgreSQL’s potential to run high-availability, large-scale data centers. Press release here.
PostgreSQL 7.4 Released
About The Author
Eugenia Loli
Ex-programmer, ex-editor in chief at OSNews.com, now a visual artist/filmmaker.
Follow me on Twitter @EugeniaLoli
This is yet another release with focus on the issues that counts.
Thank you for your work on a ISO standard compatible database for the masses. People should consider switching from closed source and OpenSource alternatives.
PostgreSQL has ben a quality product for a long time. For each release you guys make it become even bether.
Thank you!
I think 7.4 was meant to run nativelly on windows but I can’t find a mention about it?
Did they drop this or it is just delayed?
I’d like to say thanks to all of developers, contributors and testers for this great product!
Thank you!
http://techdocs.postgresql.org/guides/Windows
Quoting from that page:
The upcoming release of PostgreSQL, version 7.4, doesn’t yet natively support windows. We had made it a goal for this release, but unfortunately we didn’t get it all ready in time for the cut-off point of 7.4.
The next version of PostgreSQL after that, to be called either version 7.5 or version 8.0 will definitely support windows natively.
The main PostgreSQL project plans to add support for a native Windows version with our 7.5 or 8.0 release. This will probably be released in early 2004, with that time estimate being based on 7.4 being due for release near the end of 2003.
from what I read on the windows native support, its still going to have a cygwin.dll underneath, so its not really native at all, its still a unix hack.
if you need a good windows native opensource DB, firebird is your bet.
“from what I read on the windows native support, its still going to have a cygwin.dll underneath, so its not really native at all, its still a unix hack.”
Wrong. Cygwin is merely a wrapper over the native Windows API. So it’s still a native app. It’s no different than using a compatability or portability library, which is exactly what cygwin is.
when will PosgreSQL support multiple tablespace just like in Oracle? MySQL 4.1 already support that…
It already does, in the form of schemas.
Once again, PostgreSQL proves it is the DBMS for the seroius programmer. These changes are major, and some of them are quite interesting. Aside from the “cool” stuff, such as the performance imprevements, IPV6 datatype, etc…, one of the main things I noticed is the continued movement toward standards support, such as better support for information schema and error handling.
Also, buried in the detailed changelog is one small detail I consider major: CHECK constraints for domains. This is what was needed to make domains truly useful.
There are only 2 major missing pieces, IMHO:
1. Point-in-time recovery (essentially all the pieces are there with the WAL, so it is just a matter of putting a nice front-end onto it)
2. Nested transactions. Or savepoints, error containment, whatever you want to call it… Essentially, allowing transactions to commit a certain amount of data before continuing to other problematic operations (saves us from the need to lose thousands of successful updates, while still handling errors and maintaining whatever integrity levels we want.)
—
Yes, I know; a lot of people really want a Windows release. I personally don’t consider that an *enterprise* feature ;-). (sorry, couldn’t resist)
–It already does, in the form of schemas.
is it possible to separate datafile for each schema?
I started using PostgreSQS about six months ago. I have been really impressed with it. I am only using it for a medium sized project, but it has handled everything really well. I look forward to upgrading at some point.
No, Pg doesn’t support tablespaces, and NO, MySQL doesn’t support tablespaces.. at least not like oracle.. there’s a huge huge difference… oracle tablespaces and extends are NOT an SQL standard, and don’t need to be supported…. however I like them, and wish they are supported… I’m just clairfying to the person who said that MySQL supports them.. mysql DOESN’T… they just have different files, which means nothing.
Just go, go, go …
No, Pg doesn’t support tablespaces, and NO, MySQL doesn’t support tablespaces.. at least not like oracle.. there’s a huge huge difference… oracle tablespaces and extends are NOT an SQL standard, and don’t need to be supported…. however I like them, and wish they are supported… I’m just clairfying to the person who said that MySQL supports them.. mysql DOESN’T… they just have different files, which means nothing.
–check this out http://www.innodb.com/ibman.html#InnoDB_history
just because they support multiple files does NOT make them tablespaces.. I am fully aware of what innodb does, and multiple files != tablespaces… go read a book on oracle’s tablespace theory, and you’ll see there’s a lot of differences.
from what I read on the windows native support, its still going to have a cygwin.dll underneath, so its not really native at all, its still a unix hack.
Postgres 7.5/8.0 on Win32 will not require Cygwin. Stop spreading lies please…
I always wondered why MySQL development moves so slowly compared to PostgreSQL. This is surprising since MySQL has by far the most users.
Congratulation to the Postgre team for the excelent work!
I am a long time Firebird user and I am very pleased with the performance and the feature set it has. On the other side I see that PostgreSQL is much more popular in the open world. With every new release their feature sets are coming closer and closer to each other (and closer to Oracle too).
So let me compare just some of the new PG features with FB
Postgre:
1.High SQL92/99 compatibility
2.Hash aggregation in memory & Improvements in subquery handling
3.Enhanced implementation of functional indexes
4.New wire protocol
5.autovacuum tool
6.FullText Search
7.Replication
8.Information Schema
9.Not run natively on Windows
Firebird:
1.The same goes here
2.The same goes here
3.to be done in 2.0
4.to be done in 2.0
5.automatic Garbage Collect and Sweep (part of the server wich makes own connection to the db in separate thread)
6.Not part of the engine. (commercial addon)
7.Commercial addon – with great capabilities. If you need a spare copy for better availability the engine has a standard feature called SHADOW – live copy of the db on another machine.
8.N/A
9.Runs perfectly
Re: Tablespaces
There is work going on for tablespaces. For some reason (I lost track) they didn’t make the 7.4 cutoff, but it’s quite likely they’ll be in the next version. Remember that you can always advocate for stuff on our mailing lists: http://www.postgresql.org/lists.html (of course, features will be taken more seriously if you can code or maintain them).
Re: Firebird
Firebird is a cool database and I am happy to see that there is so much enthusiasm on various web forums for it. Please make sure the folks at the Firebird project know how much you like their database, they were looking discouraged at OSCON this year
Different databases suit different business needs, and it’s very important that no one database “take over” the whole OSS database space — even if that database were PostgreSQL! Diversity is the “Open Source way.”
Have a look http://www.mysql.com website, MaxDB has been released in same day.
However, there are no documentation and supporting. I think mysql AB quit urgent, hurry to release it (may be 7.4 has many enterprise feature)…… I am looking forward any comparsion between MAXDB(re-branded SAPDB, just copy and rename..>_<) and postgresql.
I think postgresql team puts more more effort improving alogithm and query planner… unlikey MySQL always advertise how many big company use….
Anyway, we should said GOOOD BYE for MySQL 4.0 4.1 5.0 and innoDB.com. 4.1 –> 4.1.1(alpha) more than 5 months >… and 5.0……
Thanks for the info, Josh. Also, thanks for the open attitude. We PostgreSQL users can’t thank you guys enough.
In response to Betcour above:
I don’t know if PostgreSQL has developed that much faster than MySQL, but it is really a completely different sort of software, started under completely different conditions. In fact, I think it is a disservice to both applications to make too many comparisons. Remember, the Postgres project started well before MySQL (1986, to be exact) and was a long-term research project. The whole aim of the Postgres system was to be very capable relationally, as well as very extensible. With that sort of groundwork being laid, it is only natural that so much development occurs around PostgreSQL.
Also, I think if you really could look at the numbers, you would see that while MySQL does have a greater mass of users, PostgreSQL is being used in surprisingly more places than most people realize. That includes some very big companies, as well as many smaller ones. (I have managed to migrate 3 previous employers to PostgreSQL, and am working on the latest one right now ;-))
“MySQL 4.1 already support that…”
So what? That’s an alpha release. I’m only interested in released packages for comparison anyway.
It’s nice to see PostgreSQL progressing… I last evaluated it about 2 years ago. I ended up choosing Interbase/Firebird for several reasons:
1. Native Windows port.
2. 2-phase commit. This makes it possible for the database to participate in a heterogenous transactional environment.
3. In IB/FB, database are stored in single files. This generally makes it easier to handle the database (move it around, copy/backup, transfer via FTP, etc).
I’m glad to know that the Pg team is dealing with #2 (but I haven’t checked out what the thread/process model will be, will it be multithreaded or multiprocess? Also, Pg will need to do some catching up with IB/FB with regard to Windows-development libraries/bindings, like .NET data provider, etc.
#3 was not a showstopper for me, but it is nice to have. IB/FB is also in general much easier to install and maintain for me.
Also it would be nice if Pg supported savepoints.
Firebird is a cool database and I am happy to see that there is so much enthusiasm on various web forums for it. Please make sure the folks at the Firebird project know how much you like their database, they were looking discouraged at OSCON this year
LOL, poor Firebird team
From what I can see, FB is doing well. There has been an increase of mailing list traffic over the last few months. It seems many people are beginning to be attracted and use FB more and more.
One thing that is a little shame though, they still seem to be really hung up about Mozilla using Firebird as the browser name. It’s pretty clear now that the “Mozilla Firebird” name will stick around for a while, so they should probably just let it go by now.
Also, Pg will need to do some catching up with IB/FB with regard to Windows-development libraries/bindings, like .NET data provider, etc.
Postgres does have .NET data provider
http://gborg.postgresql.org/project/npgsql/projdisplay.php
There is also one native to Mono.