Dear developers,
I wonder it happens to systems where inefficient update
SQL's are used like this:
UPDATE MyTable SET MyColumn=1234
Question arises when the value of MyColumn is already 1234
before the update.
If I am right, even when the to-be-updated column values
equal to the new values,
Happy new year!
When performing
pg_restore -L list --disable-triggers -d db1 -v my_archive
, my hard disk for Linux box (with 96MB RAM) becomes
extremely busy.
One example is that it takes more than 5 miniutes to restore
for a table from 7800 rows. Each row has less than 117
bytes in length
