Shashank Tripathi wrote: >> It's a valid discussion here (although better on -advocacy), because >> it helps >> me have the right facts to present to clients about whether they >> should stay >> with a legacy database in MySQL vs upgrading to a modern PostgreSQL. > > > For all its flaws, MySQL is catching on quick and has a very active > community of developments that several of us find rather handy - > http://forge.mysql.com/ > > Is there something similar for Pgsql? (Disclaimer: new to this group > because I'm unimpressed with MySQL beyond 30 million rows in a table > that require advanced subqueries). www.pgfoundry.org > > Shanx > > ---------------------------(end of broadcast)--------------------------- > TIP 2: Don't 'kill -9' the postmaster > -- === The PostgreSQL Company: Command Prompt, Inc. === Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240 Providing the most comprehensive PostgreSQL solutions since 1997 http://www.commandprompt.com/ Donate to the PostgreSQL Project: http://www.postgresql.org/about/donate PostgreSQL Replication: http://www.commandprompt.com/products/
