Hi Michael, Thanks for the quick reply and the pointer.
I agree 19 is not the place for a big change, so rejection works for me. The dropped column case is rejected today, that is the warning in my first mail. The child with another column order is not. Its numbers are valid for the restored table, so the data lands on other columns. v2 drops the mapping and only rejects that case. pg_dump passes the column names of the statistics object, and the restore function skips the data when they are not the names of its own columns in the same order. The child then gets WARNING: could not restore extended statistics object "public.ch_s": its columns do not match "attnames" Thanks, Shihao
v2-0003-Test-attnames-in-pg_restore_extended_stats.patch
Description: Binary data
v2-0002-pg_dump-pass-column-names-with-extended-statistic.patch
Description: Binary data
v2-0001-Let-pg_restore_extended_stats-check-the-column-na.patch
Description: Binary data
