Hackers,
recent changes have introduced the :location field to the partboundspec
in pg_catalog.pg_class. This means that if two identical tables with
identical partitioning scheme are created, but one is done before a change
to gram.y, and the other after a change to gram.y, the relpartbound fields
for those two tables could show up as different.
Can we perhaps remove the :location field here? If not, could somebody
please defend why this belongs in the catalog entries for the table? Sorry
if I am missing something obvious...
Thanks,
Mark Dilger
