ANN: Database Workbench 5.2 now includes PostgreSQL support

[Martijn Tonies (Upscene Productions)]

Upscene Productions is proud to announce the availability of
the next version of the popular multi-DBMS development tool:

" Database Workbench 5.2 "

This release includes support for PostgreSQL and adds several other features.

Database Workbench 5 comes in multiple editions with different pricing models, 
there's always a version that suits you!



"Version 5 included many new features", says Martijn Tonies, founder of Upscene 
Productions. 
"It added code editor features, has diagramming improvements, multiple 
editions, is fully HiDPI aware and offers tunnelling for MySQL and MariaDB 
connections.
The most recent version adds support for PostgreSQL, as requested by many of 
our customers."


For more information, see What's new in Database Workbench 5?
( http://www.upscene.com/database_workbench/whatsnew )


Database Workbench supports MySQL, MariaDB, Firebird, Oracle, MS SQL Server,
SQL Anywhere, NexusDB, PostgreSQL and InterBase, comes in multiple editions and 
is licensed based on
selectable modules.

It includes tools for database design, database maintenance, testing, data 
transfer,
data import & export, database migration, database compare and numerous other 
tools.


About Database Workbench
Database Workbench is a database developer tool, over 12 years in the making and
is being used by thousands of developers across the globe who have come to rely 
on it
every day. From database design, implementation, to testing and debugging, it 
will aid you 
in your daily database work.

About Upscene Productions
Based in The Netherlands, Europe, this small but dedicated company has been 
providing
database developers with useful tools for over 14 years. Slowly expanding the 
product portfolio
and gaining recognition amongst InterBase and Firebird database developers, 
they now offer
tools for a whole range of database systems, including Oracle and Microsoft SQL 
Server.

Re: MySql Swapping issues

[Jesper Wisborg Krogh]

Hi Machiel,

On 8/09/2016 05:24, Machiel Richards wrote:

...

Biggest issue at the moment is mysql taking all physical memory until
nothing left, the starts swapping as well until that is completely used up.


Since you are using MySQL 5.7, you can consider enabling memory 
instrumentation in the Performance Schema:


UPDATE performance_schema.setup_instruments SET ENABLED = 'YES' 
WHERE NAME LIKE 'memory/%';


That may help to locate where the memory is used.

To monitor the memory usage use either the sys.memory_% views 
(https://dev.mysql.com/doc/refman/5.7/en/sys-schema-views.html) or the 
Performance Schema summary tables 
(https://dev.mysql.com/doc/refman/5.7/en/memory-summary-tables.html).


Note that there is a little extra overhead instrumenting the memory.

Best regards,
Jesper Krogh
MySQL Support


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: MySql Swapping issues

[Johan De Meersman]

- Original Message -
> From: "Machiel Richards" 
> Subject: Re: MySql Swapping issues
> 
> When I monitor the MySQL processlists, there is constantly about 30-35 
> processes
> and half of them never change simply showing as :
> 
> Connect | 124678 | Waiting for an event from Coordinator

15-ish? That feels like a lot, but then I'm not particularly familiar with 
parallel replication. Might be normal for your configuration.


> The other half of the processes are queries and inserts and I can see those
> being processed and going off the list fairly regularly.

So those disconnect normally, which /should/ clean up any session memory.

I'm pretty much out of obvious things to point at. Random toughts:
 - typo in some dynamically-assigned buffer sizing (not a lot of those, though)
 - I have in the past seen memory use increase at times when the logs couldn't 
get flushed to disk; but I assume something like that would become apparent at 
restart time anyway
 - A memory leak of that size seems improbable, but it's always worth checking 
the bug reports for your server version or test other versions

Maybe someone else has some more ideas, or has seen similar behaviour?

-- 
Unhappiness is discouraged and will be corrected with kitten pictures.

-- 
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

Re: MacOS Server 5 problem after upgrade

[Matthias Schmidt]

> Am 04.09.2016 um 23:35 schrieb Reindl Harald :
> 
> 
> 
> Am 04.09.2016 um 16:17 schrieb Matthias Schmidt:
>>> Am 04.09.2016 um 16:29 schrieb Reindl Harald :
>>> 
>>> Am 04.09.2016 um 08:40 schrieb Matthias Schmidt:
 2016-09-04 15:25:19 85518 [ERROR] /usr/local/mysql/bin/mysqld: Can't 
 create/write to file '/usr/local/mysql/data/mysqld.local.pid' (Errcode: 
 102 - Operation not supported on socket)
 2016-09-04 15:25:19 85518 [ERROR] Can't start server: can't create PID 
 file: Operation not supported on socket
 
 the socket is created but then something goes wrong
>>> 
>>> that sounds like socket and pid are configured for the same location
>>> what about "rm -f /usr/local/mysql/data/mysqld.local.pid" and show us your 
>>> config
>>> 
>> 
>> thanks, that did the trick and made it run, but now I just discovered that 
>> my databases are all gone …
>> Of course I have backups, but really no experience how to get the stuff back 
>> :(
> 
> just configure “datadir” to the correct location and get familar with mysql 
> basics and your operating system

there have been 2 problems:
- the last mysql update didn’t do the update and the data folder didn’t contain 
the databases :-0
- the sock file was created in the temp folder instead of the var folder, after 
setting the sock file to the var/mysql folder all works fine

besides the control panel, it “thinks" the server is not running, although it 
is, so I guess I can delete it, as it is also not anymore distributed with the 
current versions for OS10.11


so, thanks especially to Harald, much appreciated :-)
Matthias



signature.asc
Description: Message signed with OpenPGP using GPGMail