Re: Fork DBD::mysql

2017-10-11 Thread Wm Mussatto 
On Wed, October 11, 2017 12:10, Darren Duncan wrote:
> On 2017-10-11 10:05 AM, Vincent Veyron wrote:
>> On Wed, 11 Oct 2017 15:09:49 +
>> Steven Lembark  wrote:
>>
>>> I really am curious to see any example of something in your database
>>> that
>>> can be handled more gracefully in MySQL than well-designed Pg.
>>
>> Seconded, I was wondering the same thing.
>
> While we're on that wagon, thirded.
>
> -- Darren Duncan
Haven't used Pg for a while, have they resolved the issue where it would
lockup for periods doing automatic database re-organization/table space
compression.  We used it for Bayes filtering.

--
William R. Mussatto
Systems Engineer
http://www.csz.com
909-920-9154

Re: Fork DBD::mysql

2017-10-11 Thread Darren Duncan 

On 2017-10-11 10:05 AM, Vincent Veyron wrote:

On Wed, 11 Oct 2017 15:09:49 +
Steven Lembark  wrote:


I really am curious to see any example of something in your database that
can be handled more gracefully in MySQL than well-designed Pg.


Seconded, I was wondering the same thing.


While we're on that wagon, thirded.

-- Darren Duncan

Re: Fork DBD::mysql

2017-10-11 Thread Vincent Veyron 
On Wed, 11 Oct 2017 15:09:49 +
Steven Lembark  wrote:


> I really am curious to see any example of something in your database that
> can be handled more gracefully in MySQL than well-designed Pg.
> 

Seconded, I was wondering the same thing.


-- 
Bien à vous, Vincent Veyron 

https://compta.libremen.com
Logiciel de comptabilité, libre

Re: Fork DBD::mysql

2017-10-11 Thread Steven Lembark 

> It is not as easy as it could appear. And also in some cases migration
> from MySQL/MariaDB to Pg could be problematic from performance point of
> view. One Pg developer already told us that for our use case is really
> MySQL better then Pg.

Q: What about your use case is more adapted to MySQL? 

There is no part of SQL that Pg does not support that MySQL does; there
should not be any serious performance issues with Pg that leave it 
slower than MySQL. There are a variety of ways that Pg can be faster
(e.g., partial indexes, exclusion constraints vs. triggers) and will
usually be less error-prone. You may have to refactor some sloppy design
that MySQL allowed but Pg does not, but that is also in your favor.

I really am curious to see any example of something in your database that
can be handled more gracefully in MySQL than well-designed Pg.


-- 
Steven Lembark 3646 Flora Pl
Workhorse Computing   St Louis, MO 63110
lemb...@wrkhors.com  +1 888 359 3508