jobinau

Oracle is 25 million lines of code vs 1.3 million lines of code of PostgreSQL Still Oracle don't have all basic isolation levels. Only the Read-Commited works perfect. And DDL operations are still not transactional. We should think which is inefficient design. The process model may not be very "efficient" as thread model. but it is more "stable" and more "secure". Benchmark results are not bad either.

Every software has imperfections. thats why new versions comes with improvements. There is no end to it

Yes, that is a very common case. The highest reported problem with aurora is the unexpected spikes in CPU utilization. While Same load on regular (the real) PostgreSQL is not causing any spike.

Agree. It is impossible to create a replacement for worldwide community project like PostgreSQL. It is the knowledge of humanity. Just like English literature or Any Branch of Science. We can add to it. But we cannot replace it completely.

One of the problem with temporary tables is that it will result in adding metadata information into PostgreSQL catalog (pg_class), and it will easily get bloated as the temporary table ends its life

I think the selection Tcl is a right choice than Perl. considering the Lightweight nature of Tcl

Yes, It helps a lot in Oracle to PostgreSQL migration

Suppose we want to run a complex reporting query on tables in Sales database (running MySQL) and Finance database (running PostgreSQL). What is the good option without duplicating data from one system to another?

PostgreSQL and MySQL are the most popular database systems. Yes, they can talk and share data using mysql_fdw

A summary of all the main features included in the PostgreSQL FDW so far with Illustration.

Understanding every turning knob available in PostgreSQL is important to get maximum out of PostgreSQL server.