Is there a big reason why TOAST tables are called such cryptic names?
e.g. pg_toast.pg_toast_16399
Wouldn't it be more pleasant to have them called the same thing as their
parent
e.g. pg_toast.<name>_toast
This would be very convenient for most purposes, though it would mean
we'd have to do something when
- we rename a table
- we have very long table names
...neither of which seems like such a huge pain.
It might seem like an idle moan, but the names leak out in all sorts of
places like stat tables, logs etc so converting the names to something
useful in all cases is annoying.
Alternatively, would it be possible to have both
RelationGetRelationName(onerel)
RelationGetRelationDisplayName(onerel)
the second of which would do the lookup for use in various places?
That would change lots of code however.
Comments?
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
---------------------------(end of broadcast)---------------------------
TIP 4: Have you searched our list archives?
http://archives.postgresql.org
