On 2010-10-20, at 09:15 , Kieran Kelleher wrote:

> [Bringing this twitter discussion to the mailing list...]
> 
> So, for mysql, a new user needs to pay attention to a few things so as not to 
> fall on your face with dismal performance and problems with the default 
> install, such as:
> 
> - Create a my.cnf (start with one of the example files and use the reference 
> guide to understand all the settings in the example file)
>       - Ensure innodb is default engine
>       - Pay special attention to innodb memory allocations
> 

got frustrated mainly by error messages about not enough shared memory buffers 
(or something). Otherwise, configuration was easy.

> 
> Q mentioned that PostgreSQL has a bit of a learning curve ...... so what are 
> the top few things to take care of, or gotchas, for an initial setup that is 
> exclusively used for WebObjects (if that makes any difference)

getting up and running was quick, but I'm pretty sure my setup is not optimal.

> 
> What is (are) your favorite reference website(s) for PostgreSQL?

mostly http://www.postgresql.org/docs  

> 
> What about platform-independent database dumps - does it have sth similar to 
> mysqldump that makes a SQL file that can recreate the entire server on 
> another machine and newer version?

pg_dump myDatabase > myDatabase.sql


> 
> Is replication setup as easy as mysql?
>       Is replication over SSL supported (for remote repl/backup)
> 
> How do you install? binaries, build it form source (because the binaries do 
> not have essential options for example)?

for deployment I still use http://www.entropy.ch/software/macosx/postgresql/ 
but its getting outadated.

for development, I currently using the 8.4 installation made by macports.

> 

Louis Demers eng.
www.obzerv.com


 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com

This email sent to [email protected]

Reply via email to