From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Jean-Michel Pouré <jm(at)poure(dot)com> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: 8.5 release timetable, again |
Date: | 2009-08-26 19:14:27 |
Message-ID: | 603c8f070908261214q4786162dud4a9cde7fe8a00a4@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
2009/8/26 Jean-Michel Pouré <jm(at)poure(dot)com>:
> Dear Kevin
>
>> So when you talk about focusing on usablility improvements you mean
>> that priority should be given to supporting MySQL-specific syntax
>> extensions and ensuring that there are no queries where the MySQL
>> optimizer comes up with a more efficient plan than PostgreSQL?
>
> Yes. PostgreSQL should be able to run MySQL code quoted here:
>
> This is a prerequisite for people to be willing to test and adopt
> PostgreSQL. People are not willing to debug frameworks like Drupal and
> port them to PostgreSQL. We are quite alone and lost.
Er, so we should debug Drupal for them? I find it difficult to
believe that's the best use of our time.
>> One concern I have is that you don't mention PostgreSQL configuration
>> in your performance advice, and I seem to remember you said that you
>> didn't tune your postgresql.conf file beyond boosting the
>> shared_buffers setting. If that's true, you might be somewhat
>> surprised with the performance improvements if you tweak just a few
>> other settings.
>
> shared_buffer 24M.
That doesn't actually respond to anything he said in that paragraph.
...Robert
From | Date | Subject | |
---|---|---|---|
Next Message | Josh Berkus | 2009-08-26 19:17:25 | Re: MySQL Compatibility WAS: 8.5 release timetable, again |
Previous Message | Andrew Dunstan | 2009-08-26 18:47:32 | Re: pretty print viewdefs |