Re: mysql to postgresql, performance questions - Mailing list pgsql-performance

From Thom Brown
Subject Re: mysql to postgresql, performance questions
Date
Msg-id AANLkTinNWo1V5gO5RLffUhgBIWofIc6csNZRPAOFyEMk@mail.gmail.com
Whole thread Raw
In response to Re: mysql to postgresql, performance questions  (Bruce Momjian <bruce@momjian.us>)
Responses Re: mysql to postgresql, performance questions  (Scott Marlowe <scott.marlowe@gmail.com>)
List pgsql-performance
On 31 March 2010 15:23, Bruce Momjian <bruce@momjian.us> wrote:
> James Mansion wrote:
>> Hannu Krosing wrote:
>> > Pulling the plug should not corrupt a postgreSQL database, unless it was
>> > using disks which lie about write caching.
>> >
>> Didn't we recently put the old wife's 'the disks lied' tale to bed in
>> favour of actually admiting that some well known filesystems and
>> saftware raid systems have had trouble with their write barriers?
>
> I thought the issue was that many file systems do not issue the drive
> ATAPI flush command, and I suppose drives are allowed not to flush on
> write if they honor the command.
>
> --

I thought I'd attempt to renew discussion of adding PostgreSQL support
to MythTV, but here's the response:

> It is not being actively developed to my knowledge and we have
> no intention of _ever_ committing such patches. Any work you do
> *will* be wasted.
>
> It is far more likely that we'll move to embedded mysql to ease
> the administration overhead for users.

It's a surprisingly hostile response.

Thom

pgsql-performance by date:

Previous
From: "Kevin Grittner"
Date:
Subject: Re: Aggressive autovacuuming ?
Next
From: Scott Marlowe
Date:
Subject: Re: mysql to postgresql, performance questions