On 12/21/09 11:23 AM PST, "Gauthier, Dave" wrote:
> I was wondering...
>
> In head-to-head comparisons, do DBs get stree tested, not only in terms of
> performance, but in terms of corruptions, down time, recovery time, lost data,
> etc... .?
>
> I've heard it said that MySQL is superior to My
On Mon, Dec 21, 2009 at 12:23 PM, Gauthier, Dave
wrote:
> They have ways to cope with this. Since they all code in perl/DBI, they
> could simpy open handles to the 2 DBs. Or there's an op sys level app out
> there that they could use to get the same data. But I was thinking of
> something th
ge-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of Erik Jones
Sent: Monday, December 21, 2009 12:56 PM
To: pgsql-general@postgresql.org List
Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project
On Dec 21, 2009, at 8:44 AM
On Mon, Dec 21, 2009 at 10:55 AM, Erik Jones wrote:
>
> On Dec 21, 2009, at 8:44 AM, Scott Ribe wrote:
>
>> Well, the fact that Monty secretly tried to persuade the EC toward forcing
>> Oracle to release MySQL under a license other than the GPL, while lying &
>> denying that in public, really shou
On Dec 21, 2009, at 8:44 AM, Scott Ribe wrote:
> Well, the fact that Monty secretly tried to persuade the EC toward forcing
> Oracle to release MySQL under a license other than the GPL, while lying &
> denying that in public, really shouldn't be considered a plus for MySQL, I
> would think ;-)
>
> I dont know if it's a plus or a minus, but:
Well, the fact that Monty secretly tried to persuade the EC toward forcing
Oracle to release MySQL under a license other than the GPL, while lying &
denying that in public, really shouldn't be considered a plus for MySQL, I
would think ;-)
Seriously,
> "Gauthier, Dave" :
> Again, the audience is managers. Is there an
> impartial, 3rd party evaluation of the 2 DBs out there that
> identifies PG as being more reliable? It might mention things like
> fewer incidences of corrupt tables/indexes, fewer deamon crashes,
> better recovery after syst
Merlin Moncure wrote:
It was only with the 8.x versions that postgres
really started pulling away.
Today I was re-reading a great reminder of just how true this is:
http://suckit.blog.hu/2009/09/29/postgresql_history
From the baseline provided by 8.0, PostgreSQL increased in speed by
about
Ron Mayer wrote:
* There are enough large companies that depend entirely
on each of the databases that make either one a save
choice from that point of view (Skype). And the way
Apple and Cisco use it for a number of their programs
Yeah, these are all good examples. Cisco uses Postgre
Gauthier, Dave wrote:
> The arguments against PG are not technical.
A few more points that I didn't see in this thread yet that might help
answer the non-technical questions:
* There seem to be more commercial vendors providing support
for Postgres than MySQL - because most mysql support came
pop.jaring.my]
Sent: Sunday, December 20, 2009 10:05 AM
To: Greg Smith; Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project
At 05:44 AM 12/17/2009, Greg Smith wrote:
>You've probably already found
>
Ron Mayer writes:
> Lincoln Yeoh wrote:
>> Ten or so years ago MySQL was better than Postgres95, and it would have
>> been easy to justify using MySQL over Postgres95 (which was really slow
>> and had a fair number of bugs). But Postgresql is much better than MySQL
>> now. That's just my opinion o
On Sun, Dec 20, 2009 at 3:19 PM, Ron Mayer
wrote:
> Lincoln Yeoh wrote:
>> Ten or so years ago MySQL was better than Postgres95, and it would have
>> been easy to justify using MySQL over Postgres95 (which was really slow
>> and had a fair number of bugs). But Postgresql is much better than MySQL
Lincoln Yeoh wrote:
> Ten or so years ago MySQL was better than Postgres95, and it would have
> been easy to justify using MySQL over Postgres95 (which was really slow
> and had a fair number of bugs). But Postgresql is much better than MySQL
> now. That's just my opinion of course.
Really?!?
MyS
On Sun, Dec 20, 2009 at 10:04 AM, Lincoln Yeoh wrote:
> At 05:44 AM 12/17/2009, Greg Smith wrote:
>>
>> You've probably already found
>> http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
>> which was my long treatment of this topic (and overdu
At 05:44 AM 12/17/2009, Greg Smith wrote:
You've probably already found
http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
which was my long treatment of this topic (and overdue for an update).
The main thing I intended to put into such an
At 03:19 AM 12/19/2009, David Boreham wrote:
Lincoln Yeoh wrote:
It seems you currently can only control outbound traffic from an
interface, so you'd have to set stuff on both interfaces to "shape"
upstream and downstream - this is not so convenient in some network topologies.
This is more a p
At 11:28 AM 12/18/2009, Scott Marlowe wrote:
On Thu, Dec 17, 2009 at 7:51 PM, David Boreham wrote:
> Scott Marlowe wrote:
>>
>> I would recommend using a traffic shaping router (like the one built
>> into the linux kernel and controlled by tc / iptables) to simulate a
>> long distance connection
Lincoln Yeoh wrote:
It seems you currently can only control outbound traffic from an
interface, so you'd have to set stuff on both interfaces to "shape"
upstream and downstream - this is not so convenient in some network
topologies.
This is more a property of the universe than the software ;)
On Thu, Dec 17, 2009 at 7:51 PM, David Boreham wrote:
> Scott Marlowe wrote:
>>
>> I would recommend using a traffic shaping router (like the one built
>> into the linux kernel and controlled by tc / iptables) to simulate a
>> long distance connection and testing this yourself to see which
>> repl
Scott Marlowe wrote:
I would recommend using a traffic shaping router (like the one built
into the linux kernel and controlled by tc / iptables) to simulate a
long distance connection and testing this yourself to see which
replication engine will work best for you.
Netem :
http://www.linuxfo
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> One concern I have about these trigger based replication systems is
> that I fear it may ping the slave for each and every DML statement
> separately in time and in a transaction. My slave will literall
: Thursday, December 17, 2009 11:58 AM
> To: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project
>
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: RIPEMD160
>
>
>> How difficult is it to switch the master's hat from one DB
: [GENERAL] Justifying a PG over MySQL approach to a project
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> How difficult is it to switch the master's hat from one DB instance
> to another? Let's say the master in a master-slave scenario goes
> down but the slave is fin
On Thu, Dec 17, 2009 at 12:35 PM, Madison Kelly wrote:
> Gauthier, Dave wrote:
>>
>> Hi Everyone:
>>
>>
>> Tomorrow, I will need to present to a group of managers (who know nothing
>> about DBs) why I chose to use PG over MySQL in a project, MySQL being the
>> more popular DB choice with other eng
Gauthier, Dave wrote:
Hi Everyone:
Tomorrow, I will need to present to a group of managers (who know
nothing about DBs) why I chose to use PG over MySQL in a project, MySQL
being the more popular DB choice with other engineers, and managers
fearing things that are “different” (risk). I ha
Gauthier, Dave wrote:
Hi Everyone:
Tomorrow, I will need to present to a group of managers (who know
nothing about DBs) why I chose to use PG over MySQL in a project,
MySQL being the more popular DB choice with other engineers, and
managers fearing things that are “different” (risk). I have
On Thursday 17 December 2009 09:51:19 Richard Broersma wrote:
> On Thu, Dec 17, 2009 at 8:23 AM, Gauthier, Dave
wrote:
> > How difficult is it to switch the master's hat from one DB instance to
> > another? Let's say the master in a master-slave scenario goes down but
> > the slave is fine. Can
"Gauthier, Dave" writes:
> I am more concerned with getting a robust DB replication system up and
> running. Bucardo looks pretty good, but I've just started looking at
> the options. Any suggestions?
Master Slave replication? Meaning no writes on the "sister site".
If yes, consider Londiste
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> How difficult is it to switch the master's hat from one DB instance
> to another? Let's say the master in a master-slave scenario goes
> down
On Thu, Dec 17, 2009 at 8:23 AM, Gauthier, Dave wrote:
> How difficult is it to switch the master's hat from one DB instance to
> another? Let's say the master in a master-slave scenario goes down but the
> slave is fine. Can I designate the slave as being the new master, use it for
> read/wr
: [GENERAL] Justifying a PG over MySQL approach to a project
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> - MySQL is horizontally scalable via clustering and multi-master
> replication (though
-
From: Erik Jones [mailto:ejo...@engineyard.com]
Sent: Thursday, December 17, 2009 4:42 AM
To: Craig Ringer
Cc: Gauthier, Dave; pgsql-general@postgresql.org
Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project
On Dec 16, 2009, at 10:30 PM, Craig Ringer wrote:
> - If you don&#
On Thu, Dec 17, 2009 at 3:55 PM, Gauthier, Dave wrote:
> They just called the meeting, or at least that part of it. There seems to be
> a battle brewing, some MySQL advocates are angry, concerned, fearful, ... I
> dont know why for sure.
in places like that it is inevitable. there's always goi
nd thanks to all who have contributed. Really!
-Original Message-
From: Massa, Harald Armin [mailto:c...@ghum.de]
Sent: Thursday, December 17, 2009 3:14 AM
To: Gauthier, Dave
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Justifying a PG over MySQL approach to a project
Dave,
On Wed, Dec 16, 2009 at 4:02 PM, Gauthier, Dave wrote:
> Hi Everyone:
>
> Tomorrow, I will need to present to a group of managers (who know nothing
> about DBs) why I chose to use PG over MySQL in a project, MySQL being the
> more popular DB choice with other engineers, and managers fearing things
-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> - MySQL is horizontally scalable via clustering and multi-master
> replication (though you must beware of numerous gotchas). PostgreSQL can
> be
On Dec 16, 2009, at 10:30 PM, Craig Ringer wrote:
> - If you don't care about your data, MySQL used with MyISAM is *crazy* fast
> for lots of small simple queries.
This one causes me no end of grief as too often it's simply touted as "MyISAM
is fast(er)" while leaving of the bit about "for lot
Dave,
please also check out the licence and costs terms in detail.
Especially: is it given that the planned usage willl continue to be
within the allowed bounds for MySQL-GPL? Are otherwise the costs for
MySQL-commercial budgeted or a reserve founded?
PostgreSQL has here a GIANT advantage with a
Quick question about the following statement:
"but no multi-master is on the horizion"
>From what I understand, there's several multi-master solutions such as
Bucardo, rubyrep, PgPool and PgPool II, PgCluster and Sequoia. Also
Postgres-R, which is still in development. Perhaps you just meant th
On 17/12/2009 5:02 AM, Gauthier, Dave wrote:
Hi Everyone:
Tomorrow, I will need to present to a group of managers (who know
nothing about DBs) why I chose to use PG over MySQL in a project, MySQL
being the more popular DB choice with other engineers, and managers
fearing things that are “differe
EnterpriseDB wrote a white paper called "PostgreSQL vs. MySQL: A
Comparison of Enterprise Suitability", which is fairly accessible:
http://downloads.enterprisedb.com/whitepapers/White_Paper_PostgreSQL_MySQL.pdf
Regards,
Peter Geoghegan
--
Sent via pgsql-general mailing list (pgsql-general@postg
On Dec 16, 2009, at 3:05 PM, Scott Marlowe wrote:
> On Wed, Dec 16, 2009 at 2:44 PM, Greg Smith wrote:
>> You've probably already found
>> http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
>> which was my long treatment of this topic (and ov
On Wed, Dec 16, 2009 at 2:44 PM, Greg Smith wrote:
> You've probably already found
> http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
> which was my long treatment of this topic (and overdue for an update).
>
> The main thing I intended to pu
Greg Smith writes:
> They do have a regression test suite:
> http://dev.mysql.com/doc/refman/5.0/en/mysql-test-suite.html
> But it's not really clear that they run it on every platform, i.e.
> http://ourdelta.org/hidden-tests-of-the-mysql-testsuite
They definitely don't run it on every combin
Thomas Kellerer wrote:
Greg Smith wrote on 16.12.2009 22:44:
You've probably already found
http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
which was my long treatment of this topic (and overdue for an update).
There is an update:
htt
Greg Smith wrote on 16.12.2009 22:44:
You've probably already found
http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
which was my long treatment of this topic (and overdue for an update).
There is an update:
http://wiki.postgresql.org/wik
You've probably already found
http://wiki.postgresql.org/wiki/Why_PostgreSQL_Instead_of_MySQL:_Comparing_Reliability_and_Speed_in_2007
which was my long treatment of this topic (and overdue for an update).
The main thing I intended to put into such an update when I get to it is
talking about t
Gauthier, Dave wrote on 16.12.2009 22:02:
Hi Everyone:
Tomorrow, I will need to present to a group of managers (who know
nothing about DBs) why I chose to use PG over MySQL in a project,
What kind of project is that?
If you are developing something that you are selling to other people, MySQL'
Managers want support, they can't live without. Every piece of
software has its flaws and needs patches. PostgreSQL is supported for
5 years, the latest version (8.4) will be supported at least until
2014. In total there are 6 supported version as we speak, 7.4 - 8.4.
MySQL has active suppo
Hi Everyone:
Tomorrow, I will need to present to a group of managers (who know nothing about
DBs) why I chose to use PG over MySQL in a project, MySQL being the more
popular DB choice with other engineers, and managers fearing things that are
"different" (risk). I have a few hard tecnical reas
51 matches
Mail list logo
