First in short - clustering on an index forces the physical ordering of the data to be the same as the index order of the index chosen. Since you can have only one physical order of a table, you can have only one clustered index per table and should carefully pick which index you will use to cluster on or if you even want to cluster. Unlike Microsoft SQL Server, clustering on an index in PostgreSQL does not maintain that order. You have to reapply the CLUSTER process to maintain the order. Clustering helps by reducing page seeks. Once an index search is done and found, pulling out the data on the same page is vastly faster since once you find the start point all successive data nearby is easy picking.
N. Dehouche, and A. Wongkitrungrueng. Proceedings of ANZMAC 2018: The 20th Conference of the Australian and New Zealand Marketing Academy. Adelaide (Australia), page 3--5 December. (2018)
N. Vinh, J. Epps, and J. Bailey. ICML '09: Proceedings of the 26th Annual International Conference on Machine Learning, page 1073--1080. New York, NY, USA, ACM, (2009)
M. Ackermann, and J. Blömer. Proceedings of the 20th Annual ACM-SIAM Symposium on Discrete Algorithms (SODA '09), page 1088--1097. Society for Industrial and Applied Mathematics (SIAM), (2009)