Naming conventions for views and materialized views: "*_v", "v_*", "*_mv", "mv_*" or none?

My view stores quality metrics for various gizmos1 in the database. Today I designed it to be a view. In a few years, as we produce more gizmos, it may need to be changed to a materialized view. I was thinking of naming the view either of these 3 ways: gizmo_quality_metrics gizmo_quality_metrics_v v_gizmo_quality_metrics Which one should I choose? This may need to be renamed (or not) a few years later, when switching it to a materialized view: gizmo_quality_metrics gizmo_quality_metrics_mv mv_gizmo_quality_metrics From the way I worded the question, you get the idea that I favor keeping the same name (gizmo_quality_metrics), which is based on the data, and disregard the implementation (thus, no prefixes and extensions). However, I have seen all of the above naming conventions in practice, and I am wondering what is the most maintainable one for the long term. --- 1 I am simplifying - of course, they are not gizmos. They are actually deoxyribonucleic acid (DNA) molecules, if you really want to know. But this is irrelevant. --- **[EDIT, Mar 18, 2022]** Related question (thanks to *a_horse_with_no_name* for mentioning it!): https://dba.stackexchange.com/q/154251/192715 Note that I do not link to any one particular answer in that literal *wall* of answers, from high to low rep users. It is instructive to read a few, though.