Last month, we were testing huge data loading in PostgreSQL.
We tried different options like COPY command, ETL Tool, CSV Load, and manual INSERT.

While testing this load, got to know about one more option which is the UNLOGGED Table of PostgreSQL.

Important notice: The UNLOGGED Table is not a safe because it is not written to the write-ahead log, so it is not crash safe.

If your database crash or shutdown abnormally, the UNLOGGED table may lose or truncate automatically.

But in any database system, there are few tables which always for standby, backup and snapshot purpose.
Sometimes, we need faster data loading on this kind of tables.
When you create any indexes on the UNLOGGED table, those indexes also keep UNLOGGED.

Check the below sample table, and try it yourself:

CREATE UNLOGGED TABLE tbl_TestUnlogged (ID INTEGER, Name Character Varying)