mysql vs postgresql performance code example

Example 1: mysql vs postgresql

/*Postgres is an object-relational database, while MySQL is a purely 
relational database. This means that Postgres includes features like
table inheritance and function overloading, which can be important
to certain applications. Postgres also adheres more closely to SQL
standards.

Postgres handles concurrency better than MySQL for multiple reasons:

Postgres implements Multiversion Concurrency Control (MVCC) without 
read locks Postgres supports parallel query plans that can use multiple
CPUs/cores Postgres can create indexes in a non-blocking way (through 
the CREATE INDEX CONCURRENTLY syntax), and it can create partial
indexes (for example, if you have a model with soft deletes, you
can create an index that ignores records marked as deleted) 
Postgres is known for protecting data integrity at the transaction 
level. This makes it less vulnerable to data corruption.*/

Example 2: postgresql in vs any performance

Sice 8.2 will treat them equivalently 
In fact, it converts IN (...) to = ANY (ARRAY[...]) !)