https://www.essentialsql.com/what-is-the-difference-between-where-and-having-clauses/ In fact, their functions complement each other. A WHERE clause is used is filter records from a result. The filter occurs before any groupings are made. A HAVING clause is used to filter values from a group. That means the WHERE clause is first applied to the result and then, the remaining rows summarized ...

https://www.dbrnd.com/2017/02/postgresql-how-to-disable-or-enable-foreign-key-constraint-of-a-table-data-migration-bulk-operation/ ALTER TABLE table_name DISABLE TRIGGER ALL; INSERT INTO table_name VALUES (1,6,50,60,90); ALTER TABLE table_name ENABLE TRIGGER ALL;

http://www.starkandwayne.com/blog/uuid-primary-keys-in-postgresql/ https://dba.stackexchange.com/questions/146135/psql-9-5-gen-random-uuid-not-working psql 9.5: gen_random_uuid() not working? SELECT gen_random_uuid() produces output: ERROR: function gen_random_uuid() does not exist SQL state: 42883 Hint: No function matches the given name and argument types. You might need to add explicit type casts. you can check if the functions are defined using: select * from pg_proc where proname like ‘gen_random_%’; ...

http://www.xaprb.com/blog/2009/09/12/the-difference-between-a-unique-index-and-primary-key-in-mysql/

http://dev.mysql.com/doc/refman/5.6/en/replication-options-master.html#sysvar_auto_increment_increment auto_increment_increment and auto_increment_offset are intended for use with master-to-master replication, and can be used to control the operation of AUTO_INCREMENT columns.

http://mirzmaster.wordpress.com/2009/01/16/mysql-access-denied-for-user-debian-sys-maintlocalhost/

http://dba.stackexchange.com/questions/1261/how-to-safely-change-mysql-innodb-variable-innodb-log-file-size innodb_log_file_size = 25% * innodb_buffer_pool_size, np: [mysqld] innodb_log_file_size = 64M

http://blog.suszalski.pl/2011/03/jaka-wielkosc-innodbbufferpoolsize.html innodb_buffer_pool_size < 80% RAM, np: [mysqld] innodb_buffer_pool_size = 512M