Dittos on what Sxooter said
, except I really wouldn't consider mysql, unless pgsql is not available at all (such as you don't have your own dedicated server and your host won't install it). All pgsql's additional features make life so much easier (of course you have to learn them first). I've never had any problems with corrupted indexes (or data either), nor with stability. Pgsql has performed very very well. Compiling and installing is really pretty easy - instructions are great, but installing from rpms, etc. is usually easier.
Help me choose (postgres or mysql)
Hi ,
Thanks a lot. You guys have been saviours to a "wet-behind the-ears-person-in-opensource" like me.
I have one last doubt that would help me really really decide which way to go. As mentioned before i am working on an online newspaper with around 20,0000 hits per day.
Many articles in the newspaper may exceed the 8k limit. Has this problem been overcome in postgresql 7.2 and above or not?
Could you also tell me the work around for this sitation if it still exists in 7.2 and above?
Regards
Sudeep
The 8-32K row limit was TOAST (heh) as of 7.1. The docs say any size row can be accommodated. Before that, it was still possible to get around the limit by using large objects.
http://developer.postgresql.org/docs/postgres/release-7-1.html
Well, there IS a limit. 2 gigabytes. Since PostgreSQL now uses multi-byte encoding by default, that means about 1 billion text characters.
Postgresql offers better java support than mysql, IMO.
Originally posted by Sxooter
Well, there IS a limit. 2 gigabytes. Since PostgreSQL now uses multi-byte encoding by default, that means about 1 billion text characters.
Where are you getting that? The maximum row size is (or should be) way above that.
TEXT is for strings of unlimited length, with a maximum of one gigabyte.
http://www.postgresql.org/docs/faqs/FAQ.html
It's referring to field size, not row size.
Here we go:
4.5) What is the maximum size for a row, a table, and a database?
These are the limits:
Maximum size for a database? unlimited (32 TB databases exist) Maximum size for a table? 32 TB Maximum size for a row? 1.6TB Maximum size for a field? 1 GB Maximum number of rows in a table? unlimited Maximum number of columns in a table? 250-1600 depending on column types Maximum number of indexes on a table? unlimitedOf course, these are not actually unlimited, but limited to available disk space and memory/swap space. Performance may suffer when these values get unusually large.
The maximum table size of 32 TB does not require large file support from the operating system. Large tables are stored as multiple 1 GB files so file system size limits are not important.
The maximum table size and maximum number of columns can be quadrupled by increasing the default block size to 32k.
Hi,
I have been trying to install PostGresSql 7.4.3 on Intel platform with Solaris 9 os.
It doesnt install successfully and i get the following error
Checking for Compiler default output...configure:error: Compiler cannot create executables.
I have GCC compiler 3.40 installed separately.
The config log also shows GCC not found.
Question 1
Can someone tell me what is wrong with my installation. I am new to this world of open source.
Question 2
Also can someone tell me if postgresql 7.4.3 is available as a complete package along with every dependent file like GCC etc?
Regards
Sudeep
these tools can be very useful:
www.pgadmin.org
phppgadmin.sourceforge.net
Unfortunately, a bug in compiling on Solaris was introduced somewhere in the 7.4 series. There's a post about it on hackers:
http://archives.postgresql.org/pgsql-general/2004-06/msg00535.php
Hi,
If there is a bug on PostgreqSql 7.4.3 while building it on Solaris 9.0, can you lead me to proper installation instructions for building PostgreqSql 7.3 on Intel platform on Solaris 9 os.
Regards
Sudeep
Hi,
If there is a bug on PostgreqSql 7.4.3 while building it on Solaris 9.0, can you lead me to proper installation instructions for building PostgreqSql 7.3 on Intel platform on Solaris 9 os.
Regards
Sudeep
You did read the link I posted, right? The only two fixes right now are to either download the CVS tip of 7.4 or to apply the patch listed in the message I posted the link to.
But, according to that message this should be fixed in 7.4.3, so I'm not sure what the problem is. I'd ask on the pgsql-admin list.