[mythtv] More ideas on PostgreSQL support, comments welcome

[Michael T. Dean]

On 09/06/2004 07:59 PM, Robert Middleswarth wrote:

> Torbjörn Jansson wrote:
>
>>>> Funny, I've never had a table "randomly" corrupted.   I myself prefer
>>>> Postgres over MySQL, but MySQL works just fine for Myth in my
>>>> experience.     
>>>
>>> I have.  Under DSpam it pushes the database hard with lots of records
>>> added / modified and over time it just seems to give up I
>>> have to repair
>>> all the tables and seem to fix the problems.  It is rear and has been
>>> fixable for me but it does happen.  
>>
>> I use dspam too, and i have never seen it randomly corupt the mysql db.
>> The only time i've had mysql db corruption is when mysql has been 
>> shutdown
>> uncleanly (hw lockup for example) or when i had disk corruption.
>
> Although Off topic I started having the problem when I switched from 
> redhat 9 to Debian testing might be some setting related to that but I 
> was just answering the question.  I think it might be related to the 
> default setting under debian but I see it every few weeks.  I justed 
> changed out the system last week because I was upgrading but I had 
> uptime of 7 Months I don't think it was hardware related.  In the end 
> I doubt it would effect myth as my problems seem to happen when the 
> records hit way over 1 million records and even the tv data wouldn't 
> get close to that.

Name a program and I can probably figure out how to configure it/the 
machine it runs on to cause it to randomly corrupt data.  Configure a 
program so it won't corrupt data, and I can probably configure the 
machine it's on in such a way that the program corrupts data anyway.

In other words, these comparisons are apples and oranges.  The 
application is one small part of the system, *everything* on the system 
affects the rest of the system, and no two open source systems are 
identical (as a matter of fact, the same holds true even for proprietary 
systems).

MySQL data is randomly corrupted on some machines and not on others.  
Saying MySQL corrupts the data may be blaming the innocent unless you 
can actually point to a bug in MySQL that's causing the corruption (in 
which case you should be writing patches instead of writing posts about 
how PostgreSQL is more stable than MySQL--that's what OSS is all about ;).

PostgreSQL may be more stable than MySQL on a machine built/administered 
by someone who has more experience with/knowledge of PostgreSQL.  This 
might be a good reason to allow the user to choose his/her database, but 
not if adding Postgres support is detrimental to the 
design/stability/usability of MythTV.

I think (hope) that pretty much summarizes and closes out this thread...

Mike