Mark Dilger <mark.dil...@enterprisedb.com> writes: > CopyStatistics seems to just copy Form_pg_statistic without regard for > who owns the toast. Is this safe?
No less so than a ton of other places that insert values that might've
come from on-disk storage. heap_toast_insert_or_update() is responsible
for dealing with the problem. These days it looks like it's actually
toast_tuple_init() that takes care of dereferencing previously-toasted
values during an INSERT.
regards, tom lane
