From: Hannu Krosing <hannu@2ndquadrant.com>
To: Yeb Havinga <yebhavinga@gmail.com>
Cc: Greg Smith <greg@2ndquadrant.com>
Cc: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Ross J. Reedstrom <reedstrm@rice.edu>
Cc: pgsql-performance@postgresql.org
Subject: Re: mysql to postgresql, performance questions
Date: Wed, 24 Mar 2010 10:59:58 +0200
Message-ID: <1269421198.11473.50.camel@hvost> (raw)
In-Reply-To: <4BA9D39B.6020103@gmail.com>
References: <4BA23936.2030507@gmail.com>
<4BA596D2.4050406@squeakycode.net>
<20100323185232.GD6662@rice.edu>
<5342.1269372121@sss.pgh.pa.us>
<4BA934B9.9070401@2ndquadrant.com>
<4BA9D39B.6020103@gmail.com>
On Wed, 2010-03-24 at 09:55 +0100, Yeb Havinga wrote:
> Greg Smith wrote:
> > Tom Lane wrote:
> >> So has anyone looked at porting MythTV to PG?
> >>
> >
> > Periodically someone hacks together something that works, last big
> > effort I'm aware of was in 2006, and then it bit rots away. I'm sure
> > we'd get some user uptake on the result--MySQL corruption is one of
> > the top ten cause of a MythTV system crashing.
> It would be the same with PG, unless the pg cluster configuration with
> mythtv would come with a properly configured WAL - I had corrupted
> tables (and a personal wiki entry (the other mysql database in my
> house) *only* when I sometimes took the risk of not shutting down the
> machine properly when e.g. the remote was missing).
Pulling the plug should not corrupt a postgreSQL database, unless it was
using disks which lie about write caching.
Now need for WAL replica for that
> regards,
> Yeb Havinga
>
--
Hannu Krosing http://www.2ndQuadrant.com
PostgreSQL Scalability and Availability
Services, Consulting and Training
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: hannu@2ndquadrant.com, yebhavinga@gmail.com, greg@2ndquadrant.com, tgl@sss.pgh.pa.us, reedstrm@rice.edu
Subject: Re: mysql to postgresql, performance questions
In-Reply-To: <1269421198.11473.50.camel@hvost>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox