Sun Announces Support for PostgreSQL 283
jadavis writes "Sun announces 24x7 support for PostgreSQL on Solaris 10. From the article: 'Today Sun announced that it will be integrating the Postgres open source data base into the Solaris 10 OS and providing world-wide 24x7 support for customers who wish to develop and deploy open source database solutions into their enterprise environments. Sun is working with the PostgresSQL community to take advantage of the advanced technologies in the Solaris 10 OS, such as Predictive Self-Healing, Solaris Containers and Solaris Dynamic Tracing (DTrace).'"
Progressive... (Score:5, Funny)
Re:Progressive... (Score:5, Insightful)
What's next, will solaris understand cursor keys? Ship with BASH? What's the world comming to?
Solaris has shipped with bash for quite a while now...
Re:Progressive... (Score:5, Interesting)
Re:Progressive... (Score:3, Informative)
Re:Progressive... (Score:3, Insightful)
Besides - With Sun we were paying all that money and never had to make use of it - with Dell, you regularly get to feel like you're getting something for your support money
Re:Progressive... (Score:2, Interesting)
I think it's shipped with bash since Solaris 7. It's definitely been there since Solaris 8 (/bin/bash).
If only Sun's PHBs had listened to the engineers, PostgreSQL could have been shipping with Solaris at least two years ago.
Sun's PHBs move in mysterious ways.
Re:Progressive... (Score:5, Insightful)
Actually, they don't. What is going on, is a inside fight.
There is a group there that fears MS (rightly so). They think that dealing with MS is dealing with the devil. They really want to crush them at all costs. This group pushes Sun towards the OSS path. The group is also responsible for the approach with OpenOffice as well as Java. Problem is, that MS won the desktop sometime ago, and is entrenched. Taking it back is a very difficult thing to do. As to server space, They do not see MS is taking from them (probably right). That group is helping linux.
The other group sees Linux taking from them (rightly so). Linux has been eating up server space. They are taking away from Solaris. This group did open solaris as a way of winning very lucrative support contracts and hopefully to sell hardware. One of the keys here is to try and make Solaris more like Linux. So they are trying to adopt a number of OSS and claim that they deserve the OSS worlds support. What is interesting is that they are starting to support BSD (I am not sure if they are looking to take it over or as support against Linux; more like a long-term trojan horse).
So what does it mean? That Sun is like any other large firm. There are multiple fractions playing games in house and McNeally lets it go.
Re:Progressive... (Score:2, Informative)
Re:Progressive... (Score:3, Interesting)
But, this thread was describing Sun's PHBs. Your PHB's finally agreed to open this not because they found relgion, but because they want sales. To say otherwise would be disingenuous.
BTW, That is no
Re:Progressive... (Score:3, Interesting)
Sun and BSD (Score:3, Interesting)
As a result, their are probably elements of a BSD culture in Sun.
In addition, the GPL space makes it harder for a traditional software player to compete. The GPL makes sense for PURE hardware players (of which Sun is not, and in
Re:Sun and BSD (Score:2)
BSD is corporate friendly, iff you want the same game that has all but destroyed the unix market. That is, the ability to close off the work from your competitors as soon as it is in your advantage. Personally, the whole fiasco over unix taught me that it is a losing situation and one that I will no longer do. GPL works better for suppliers as it prevents anybody from being able to take away and not give. It is also better from consumers as it prevents one company
More links (Score:5, Informative)
http://www.sun.com/software/solaris/news/111705.j
More about Postgres specifically:
http://www.sun.com/software/solaris/postgres.jsp [sun.com]
Sun Blog about improving performance (Score:5, Informative)
Re:Sun Blog about improving performance (Score:3, Interesting)
Re:Sun Blog about improving performance (Score:3, Funny)
It can see into the future (Score:5, Interesting)
Yes, this is a technology that is able to predict when breaks will happen, and carry out the repairs before the problems ever surface.
Re:It can see into the future (Score:2)
Who knew that the HAL-9000 ("2001" reference) would actually be made by SUN Microsystems?
SUN has made some great moves (Opteron-based workstations and servers), great new UltraSparc (T1) processors, a rock solid OS that they have open sourced (Solaris 10), and now their alignment with PostgresSQL. I am truly impressed. It looks like they have made all the right moves. Perhaps they have used SGI (Silicon Graphics) as an object lesson as to "what NOT to
Much bigger than just Postgres (Score:5, Interesting)
Re:Opensolaris is being done all wrong (Score:2)
Second, this is their commercial solaris. It is what is offered. They will sell you support on top of it. Basically, they are competing against Linux with this.
Third, while I am mostly a Linux hacker (and certainly where my loyalitys lie), Solaris is without a doubt a solid OS.
So my question to you, is why do you think it is subpar? Because, it does not have the latest and gre
Re:Opensolaris is being done all wrong (Score:2)
Re:Much bigger than just Postgres (Score:2)
An honest question. (Score:3, Insightful)
Re:An honest question. (Score:3)
My past beef with Sun was the shoddy x86 support (remember Solaris 8 x86 that aptly deserved the moniker slowaris?) and negative approach to Linux. Since their recent adoption of AMD X86-64, less doublespeak on Linux, and OSS-ing of Solaris though, I'm willing to take another look.
Maybe they are starting to wake up and smell the coffee......java per
Re:An honest question. (Score:2)
Re:An honest question. (Score:2)
Re:An honest question. (Score:2, Funny)
People trying to do stuff?
Re:An honest question. (Score:3, Informative)
The shift will probably start happing in the next year or so... then we'll have to buy another sparc box to support it (any excuse...)
Re:An honest question. (Score:2)
Re:An honest question. (Score:2, Informative)
If it wasn't for DTrace, Zones, and ZFS I would stick with Solaris 8 for even longe
Re:An honest question. (Score:2)
Re:An honest question. (Score:3, Informative)
I am not saying that I am going to run Solaris 8 forever. I am just saying that I am speeding up the transition to Solaris 10 only because of the features it offers. They make my life as sysadmin much easier.
Re:An honest question. (Score:2)
Re:An honest question. (Score:5, Interesting)
Who uses Solaris 10?
I assume you mean "uses it instead of Linux", what with this being Slashdot. How about people who've benchmarked it against Linux and found Solaris to scale better and more smoothly? Some of us like having beefy Sparc or Opteron SMP machines that perform predictably with Solaris, rather than the erratic behaviour we've seen with Linux on SMP Intel hardware. The 2.6.x Linux kernel has also been a serious disappointment in terms of reliability, a definite step back from 2.4.x.
Re:An honest question. (Score:2, Informative)
interesting. Do you remember when Sun was going to release OpenSolaris and they held back. The reason they held back was that internal benchmarking found that Linux 2.6 was killing everything that they had. They had to redesign and recode their networking (according to a friend of mine who did this, they borrowed heavily from the OSS world for ideas; but he swears it will beat them for a while). In addi
Re:An honest question. (Score:3, Informative)
Now, we are in the same boat. I made several claims that one OS sucks yet I didn't list any references to support my claim.
That force me to discount your entire statment and all creditability.
Solaris 10 is a very nice OS, but my Oracle 10g RAC runs quite nicely on RHEL3 x86-64. (SMP Opterons (DBs) and SMP Xeon (app
Re:An honest question. (Score:2, Interesting)
It's too bad you got modded "flamebait" (Score:4, Insightful)
Our shop is mostly Solaris (8) and RHEL with Oracle 9i. We're currently looking at upgrading our Solaris boxes to Solaris 10.
The problem? Oracle 9i is not supported on Solaris 10. It's supported on RHEL and earlier versions of Solaris.
So at the moment, it's not doable for us. But from the tinkering I've done with Solaris 10, it's actually pretty cool. I've got it running on an Ultra 10 under my desk and have been evaluating ot for a couple of months now. I'll tell you it's much lighter than previous Solaris versions (well, 7 on. 2.6 was pretty zippy in comparison later versions).
Goodbye to Oracle ? (Score:2, Insightful)
Re:Goodbye to Oracle ? (Score:5, Informative)
Here's the deal. The company where I'm the SysAdmin has 3 databases we support - DB2 (Linux and AIX), SQL Server (financial product decision made outside of our department without our consultation) and PostgreSQL.
DB2 runs our core database for our enterprise application. All databases were investigated at the onset of this project and DB2 came out on top. SQL Server is in house for a shitty financial package (Navision) and another legacy system. PostgreSQL is our data warehouse.
Because of some issues surrounding our DBA team and the fact that SysAdmins often have to cameo as DBAs in a quick pinch, I've come to learn quite a bit about DB2. It has its warts and bugs but it's 100 times more robust than PostgreSQL and 1000 times more robust than MySQL (which we use for a few self-managed databases here and there - intranet stuff/nagios).
We're currently migrating our data warehouse to a new hardware set and at the same time upgrading from 8.0.3 to 8.1 of PostgreSQL. This requires a restore of the database to migrate. This 80GB datawarehouse took the better part of a day to restore on a box that was 10 times faster than the original. Reading from different volumes on different controllers on our SAN on an x445 with 8 CPUs and 16GB of memory took 8 hours to restore!
This box used to run DB2 on Linux (we just migrated to AIX and a new SAN) and could restore a 100GB production database in 45 minutes.
The box wasn't being used. I/O wait was at 1% the entire time. Each of the 8 CPUs was 90% idle the entire time. Of course memory was maxed out because PostgreSQL uses the OS to cache for it but we weren't using any swap. This was using the native PostgreSQL compressed backup format.
Oddly enough for PostgreSQL, I had less insight into what the database was doing during that time than I would have with DB2.
In DB2 I can make memory changes on the fly - db cfg, dbm cfg and speed this process up. I can use db2mtrk to see what my memory is doing. I have things like bufferpools to allocate memory where it's really needed.
With postgresql, I can change a text file (which I love) but have to restart postgres for a lot of them to take effect. Some db2 changes require an instance restart as well but not many anymore.
Some of the problem lay with me and I'll admit that but some also lay with PostgreSQL.
The whole point is that DB2 and Oracle don't normally go after the same market as MySQL and PostgreSQL. Are there companies using those databases in place of DB2 or Oracle? Sure. And I'm sure they're very happy and have a nice humming system. Our warehouse runs wonderfully on PostgreSQL and there are no complaints but more often than not, the markets simply don't intersect.
kill -HUP? (Score:3, Informative)
Fix me if I'm wrong, i didn't use this feature much. But it worked for me when I needed it.
--Coder
Re:kill -HUP? (Score:2)
There may be configuration parameters that this won't reset, but I haven't changed enough during runtime to know.
Re:Goodbye to Oracle ? (Score:3, Informative)
You may want to check out the comments about the "checkpoint_segments" configuration parameter here [sun.com]; tweaking that appears to improve bulk loading performance considerably.
PostgreSQL is doing a fine job for my database [blogs.com], although it's a much smaller installation than yours. Only 4M records, but, hey.
Re:Goodbye to Oracle ? (Score:3, Interesting)
Our biggest fact table has 48M rows if I'm not mistaken. It might actually be larger than that. As a side note about 1/3rd of that table gets updated every night as part of our warehouse load. Vacuums are a killer for us.
One thing I did read is that you could disable fsync for the restore process. We may just make that a normal documented task anyway.
On yet another note, since we're moving to new hardware, one thing
Re:Goodbye to Oracle ? (Score:2)
Populating a Database [postgresql.org]
Re:Goodbye to Oracle ? (Score:2)
The problem is this:
While we qualify for a midsize company in terms of staff, our revenue and accounting volume ranks in the Fortune 100 range. Navision was a shitty choice from the start.
Nope - this is Sun's revenge at IBM (Score:2)
Lets face it - Oracle isnt kicking Sun's butt - its IBM. Ever since the dot com bubble burst and IBM finally found its game, the sun has been setting (or eclipsed (ha-ha!)) with IBM stealing more and more of Sun's customers and grabbing new accounts. Part of the problem for Sun is that IBM has the ability to sell solutions. You want a software stack to handle applications? IBM has it (WebSphere, DB2, etc). You want a software stack to manage infrastructure? IBM has that too (all the Tivoli stuff). You want
Re:Goodbye to Oracle ? (Score:2)
Walla? Walla? You have got to be kidding.
Sun opening up? (Score:3, Interesting)
Sun haven't been particularly enthusiastic about open source in the past. Most of the time they give the impressiosn of not really knowing what to do with it - like a kid with a really great new toy only they don't know how to use it. Take OO.o for example and the older funky licensing. They seemed to suffer from some weird love-hate dichotomy.
Sun used to be real big, well, I mean "bigger" - but really lost their way. Now we have Open Solaris, re-licensed OO.o, the funky new Niagra uber-processor (can't wait to see if^H^Hhow it works) and now what appears to be a very cool corporate offering of a OSS database - and a commitment to commit all modifications back to the project as well.
Did someone at Sun suffer from one of those wossnames...epithany thingies?
Re:Sun opening up? (Score:2, Informative)
Sun haven't been particularly enthusiastic about open source in the past.
The thing is, Sun has had to do a lot of work behind the scenes to get to where it is today on Open Source.
For example, it's about half a decade now since the project to open-source Solaris was started. There was an incredible amount of legal, engineering and commercial work to be done to get there.
These things don't happen on a whim.
Re:Sun opening up? (Score:3, Insightful)
We're not some "hegemony". We're a very collection of factions with conflicting experiences , sensibilities and interests.
I would love Postgres to knock the wind out of Oracle. A price cut would be very handy. I coulud spend some money on hardware rather than sending it all to Ellison.
Re:Sun opening up? (Score:5, Insightful)
Opening up? Things to come?
Sun has been one of the biggest commercial open source supporters for years now. Probably only surpassed by IBM and the Linux companies ( RedHat and Suse, Linux is their core business after all ).
Millions to buy StarOffice, millions to setup and run OO.org and OpenDocument development, marketing, promoting OpenDocument. Releasing packages like GridEngine, etc. http://www.sunsource.net/ [sunsource.net]. Years of shipping and support opensource applications to companies that would never have used it otherwise.
Back when I was a network admin, we got a whole lot of GNU software in the system by first showing superiors that Sun endorsed those packages and actually provided solaris binaries.
Sun's main issue is PR, I suspect. When IBM does something good, it makes sure everyone knows. But that doesn't seem to be McNealy's style...
Don't bother (Score:3, Funny)
That sound you hear, to coin a phrase, is Sun, cutting off Red Hat's air supply.
Re:Don't bother (Score:2)
Wondering... (Score:2, Funny)
What did you do in the database wars? (Score:5, Interesting)
How will MySQL respond? I'd be sad to lose our investment over the last five years, but commercially the words "Oracle" or "Sun" just radiate comfort factor to less well informed customers.
Re:What did you do in the database wars? (Score:2)
Re:What did you do in the database wars? (Score:2)
I have been running PGSQL on Linux since the 6.0 series. I would consider myself a prime candidate (small company, we run all of our customer service and core telecommunications service products (IVR) on top of the PGSQL database. I just don't see enough value-add to buy Sun equipment to run their flav
Re:What did you do in the database wars? (Score:2)
Sun supporting Postgres is not aiming at the low-end. MySQL will continue to develop features they told us we didn't need and Postgres has had for years.
Meanwhile moving to Postgres won't be that difficult. You'll probably find a few features that make it so you no longer need a few ugly hacks.
PostgreSQL is a NICE package... (Score:5, Interesting)
First, just do a straight port, get PostgreSQL running your MySQL data.
Buy a beefier server, because at this stage, PostgreSQL WILL be slower. For raw reading of simple databases (the old joke that MySQL isn't a real database isn't AS true anymore, but is in the ideas), MySQL is faster. PostgreSQL shines as you build more complicated system.
Second, use explain and start optimizing your system. MySQL develop tends to do series of queries, because the MySQL protocol is nearly "free." Doing 5 queries and doing the joins in the software in MySQL tends to be fast, but is REALLY slow in PostgreSQL. So start building more complicated queries using joins server side. At this stage, PostgreSQL catches up (or nearly so) with MySQL.
Third, learn PL/pgSQL. This lets you do a LOT of optimizations with triggers and functions. For example, if you need to look things up in 3 tables to get the Primary Keys, then query a third table, in MySQL you do 3 SELECTS, store the values in variables, then the final SELECT to get the data. In PostgreSQL that would be painfully slow (the connection costs kill you), so you do a massive join, which is okay if you have enough RAM and configure PostgreSQL to use it, but it sucks up memory. Then you build the PL/pgSQL function. This lets you do it the "old way" grabbing the data, keeping it in variables INSIDE the database, then doing the query. This is REALLY REALLY REALLY fast in PostgreSQL, keeps the RAM usage reasonable, etc. Sure you can throw 4-8 GBs at RAM cheaply, but when you start doing a bunch of really big JOINs and SORTs, you can't always get PostgreSQL to use it smartly.
Fourth, at triggers whereever possible. If you ever run a COUNT or other aggregate, re-think. For example, in a forum (trivial case, but fun), you may want to display the number of threads in a topic. Well, running a SELECT COUNT(*) on the threads JOIN topics will BE BALLS slow on PostgreSQL... HOWEVER, you instead do a trigger that keeps a count in the TOPIC called threads. You would do this in MySQL by having a second INSERT when you do a thread, but in PostgreSQL, you let the database handle it. ON INSERT to THREADS, find the topic and thread_count
Also, optimize your INSERTs. In areas where you currently check IF "is this already here" THEN UPDATE ELSE INSERT, you do that in stored Functions. function insert_or_update (values) that does an UPDATE and if it fails, INSERT, or otherwise does the logic server side.
Once you learn to do real database programming, even at the rudimentary level I described, PostgreSQL SCREAMS. If you are building web sites/web applications, they SCREAM. However, if you treat PostgreSQL the way most treat MySQL, as a data dump, you'll be miserable at the performance.
Final neat idea that we never implemented... but will one day. We were planning to use PL/php (there is a PL/perl) for a performance hack. For each major script that does a bunch of queries, even with optimizations, there is a final hack you COULD THEORETICALLY do... this is a hack, admittedly. Basically, instead of doing queries, define an associated array with all the data you want. In development, do a bunch of queries and put the data into the array, then process it. For optimization, move those queries to the server. Then you build the array in PL/php, serialize it, and return it as text. Now you call the PL/php function (SELECT get_FooPage_Info(page_identifier) that returns a text value, the serialized array. Now you have one database connection, it does ALL the work INSIDE the database process, and in PHP land, you just work off the array).
PostgreSQL is EXTREMELY powerful for areas where most people use
Application tuning suggestions (Score:3, Informative)
Ok, there are a few areas where PostgreSQL performance sucks. Try doing an outer join between a moderately sized table (few million rows) and an empty table (zero rows). The result will be a nested loop join which will eat up your processor time for an insanely large time. The answer here is either to add a row to the empty table and vacuum analyze or rewrite your query to avoid the join against the empty table since
Re:Application tuning suggestions (Score:3, Insightful)
But the original poster was talking about having complex _PHP_ stored procedures to do stuff - see the last two paragraphs.
Well, I think that is a stupid idea but not for reasons of performance.
MySQL devs are always thinking of one db per app and one app per db. When you do things this way, it doesn't really matter *where* you put the code. But most db's don't evolve to be a single app db. Often you are running multiple apps against that DB after a while.
And in these cases, it is important to cleanly sep
OS dependant OSS Support (Score:2)
What I wonder is if you should get such support and just use it as fallback for your problems on different architectures. That way you could test if your problem is specific to your setup and if you can reproduce it, you can use Suns fix and port it back to your re
This is beautiful. (Score:2)
I moved to PosgreSQL 2 years ago, and this has re-affirmed my confidence in Sun in embracing open source initiatives.
I guess it was absolutely something that had to happen, to re-invent yourself. IBM did it, Apple did it.
The future for Sun should be interesting in the next couple of years, I most certainly will be watching.
Maybe we should buy shares in Sun? Sitti
And Oracle just endorsed Open Solaris (Score:2)
Independantly, Oracle bought the company the provides the innobase substructure for MySQL.
--dave
I wonder what Oracle thinks about this? (Score:2)
Re:I wonder what Oracle thinks about this? (Score:2)
Sun seems to finally be getting it. (Score:5, Interesting)
Finally. Sun hasn't shipped a C compiler with its OS since SunOS 4.1.3 (circa 1990).
Re:Sun seems to finally be getting it. (Score:4, Interesting)
Anyone who compares two apps on sparc-solaris and x86-linux should really keep this in mind...
Debian Solaris (Score:2)
Re:Debian Solaris (Score:3, Informative)
Re:Debian Solaris (Score:2)
Re:Debian Solaris (Score:2)
Re:Debian Solaris (Score:2)
Re:Debian Solaris (Score:2)
Re:Debian Solaris (Score:2)
If the "Red Hat" container can run RH binaries, what stops you from installing Debian libraries in Debian-named directories with Debian config files? That's most of the Debian Solaris
Postgres - Oracle? (Score:3, Interesting)
When Sun didn't want to compete w/Oracle ... (Score:2)
Oh well.
So confused -- Sun becomes more evil by supporting PostgreSQL ?
Re:Trolltrain leaving at platform 9... (Score:2, Funny)
Flat-files and grep is superior to MySQL.
Re:Fucking great. (Score:2)
Maybe the few millions users of solaris do actually care?
Tip: What you don't care about may have some interest for someone else.
In other words: You are not the center of the world (even though it looks like it from you narrow point of view).
Re:Fucking great. (Score:2, Insightful)
It is exciting news for Postgres users. The prospect of Sun coming aboard and actually contributing is great. And 24x7 support will get more people aboard.
Re:PostgreSQL is good (Score:2, Funny)
Re:PostgreSQL is good (Score:2)
One advantage to firebird is that it has an embedded version whilst PostgreSQL doesn't.
Currently I use SQLite but I am thinking of moving to firebird embedded for its extra functionality.
Re:PostgreSQL is good (Score:2, Informative)
I've used both firebird and postgresql for the last 7 years or so. My only complaint with firebird was that the Java JDBC driver was so much slower than the postgresql driver (this was a couple of years ago). I've been using PostgreSQL exclusively for the past 3 years or so. It isn't as easy to admin as Firebird, but also offers more functionality. For example, PostgreSQL lets you define procedures in nearly any language (python, perl, java,
Re:Why MySQL and not PostgreSQL? (Score:2, Informative)
Nice GUI admin tool. I like that much better than silly web applications.
beeing multiuser is just as easy in postgresql as mysql..
But if you for some unknown reason must have a web tool, there is phppgadmin [sourceforge.net]
Re:Why MySQL and not PostgreSQL? (Score:3, Interesting)
Clearly, Postgres works fine in multi-user installations. I am inferring that you probably mean that MySQL is easier to administer in the kind of multi-customer environments you have on boxes doing web hosting duty.
Of course, I have no idea whether this is true or not, since that's not the business I'm in. However, I suspect the historical popularity of MySQL as a rudimentary, low footprint data store for dynamic web sites means that there is more expertise in
Re:Why MySQL and not PostgreSQL? (Score:2, Informative)
Yes, you think that's insecure, but the truth of the matter is that giving individual users their own MySQL username and password does not make it any less insecure. I am of the opinion that it's better not to lull people into a false sense of security: if they can see how sharp the blade is, they will be more careful whe
Re:Why MySQL and not PostgreSQL? (Score:4, Insightful)
Yes, you think that's insecure, but the truth of the matter is that giving individual users their own MySQL username and password does not make it any less insecure. I am of the opinion that it's better not to lull people into a false sense of security: if they can see how sharp the blade is, they will be more careful when using a powerful tool.
That's a really bad idea IMO.
Fact: it's trivial for any user with an account on a box to read any other user's files, even in their cgi-bin, since they must necessarily all be visible to the Apache daemon user {www-data on Debian systems}.
That's not a fact, but it is the sign the server hasn't been configured very well.
The only way around this is for every user to run their own instance of the Apache server as themself, on a different non-privileged port; and to have a transparent proxy on port 80 that redirects requests to the appropriate port based on the host name.
Shared web hosting platforms should really be using some implementation of per-customer compartmentalisation at the OS level if the users are allowed SSH access, or to run CGI's. Solaris 10 supports this natively, there are at least two separate native implementations of something very similar for Linux, Windows 2003 even supports this to some degree I gather (though not to quite the same extent) and then there are tools like VMWare.
Of course, running your MySQL server on an entirely separate hardware from your web server is also a Good Thing(TM), especially when someone manages to (most likely inadvertently) DoS your SQL server.
However, failing that, any web server used by multiple customers to run CGI's should at the very least be configured to use something like suexec, which has been a standard feature of Apache for about 8 years or so.
Using suexec (or gsexec, or cgwrap, or similar tool as appropriate for whatever web server your using) is precisely intended to prevent CGI's running as one user from accessing or modifying files (including other CGI's) that belong to another user.
Re:Why MySQL and not PostgreSQL? (Score:2)
Why would you do that? Instead, create a new secondary group for each customer, and put only them and Apache into that group. chgrp all of their web files to that group. Give said files mode 640. Voila: Apache can read (but not write) all of their web data, but nothing in their home directory.
Re:Why MySQL and not PostgreSQL? (Score:2, Interesting)
Re:Why MySQL and not PostgreSQL? (Score:2)
A list of webhosts that support pgsql.
Re:Why MySQL and not PostgreSQL? (Score:4, Informative)
Re:Why MySQL and not PostgreSQL? (Score:2)
but i don't think you should choose a database by how hard it is to set up (people that 5 years ago tried to install oracle on redhat , like me, know what means a hard to set up database), instead you should choose the database by it's capabilities for your applications. if you need simple fast selects, go mysql, if you need very deep r
swing (Score:5, Informative)
Sometimes I think Sun really didn't think out the Java GUI experience very well before implementing it. The reason you get those blank screens during load times is how swing threads. It uses the same thread for event handling as for screen redrawing. From a programming stand point, I'm sure it makes it much simplier to use their API's for simple GUI's. However, when you've got tools written for system administration that will almost definatly take some time to process an event, it makes for a bad end user experience. Java is a great language. However, their poor implementation of the GUI API's makes the end user experience bad. And ultimately people who use java programs think the whole language sucks because of a bad user experience with the GUI.
Re:sun will need to make BIG changes (Score:5, Insightful)
Done. Sun released Studio 11 (http://www.sun.com/software/products/studio/inde
- ultrasparc performance is terrible. Address it.
Done. The UltraSPARC-IV+ chip (http://www.sun.com/processors/UltraSPARC-IVplus/ [sun.com]
- get the X11 libraries and headers fixed - completely
Done. Solaris 10 (at least on X86) uses the Xorg implementation. The previous Xsun implementation is also available if you need it, though.
- Get ldap working without so many support applications
I can't say that I understand this one. Sun's Directory Server is the best performing and most scalable server available. It's very in-line with the standards so any LDAPv3-compliant application should work with it just fine. It is the preferred directory for use with most commercial LDAP-enabled applications.
- make your platform work better with OSS software (eg: gcc)
What else needs to be done in this area? Solaris 10 ships with a lot of OSS software, including GCC, and Sun makes a lot of additional OSS software available on the Companion CD (http://www.sun.com/software/solaris/freeware/ [sun.com]). If that's not enough, you can use the SunFreeware (http://www.sunfreeware.com/ [sunfreeware.com]) or Blastwave (http://www.blastwave.org/ [blastwave.org]) collections to get what you need.
Re:That's amusing. (Score:2)
I just downloaded Sun's Studio 11 package, no license manager in sight (which, iirc, stopped with Workshop 6 Update 2). The software is available for a free download, but support will cost
Postgres was an Object Oriented Database (Score:2, Informative)
Re:PostgreSQL and C#? (Score:2)
Re:PostgreSQL and C#? (Score:2)
Re:Solaris worth trying for a redhat based system? (Score:2)
Only if you like java GUIs for configuration. We've got Solaris 9 on a dhcp server and can't configure it if we don't also have java installed because all the config tools require java.
I don't know if Solaris 10 is the same way.