Simon Riggs <si...@2ndquadrant.com> writes:
> It's possible to set toast reloptions for tables that don't have toast
> tables at all. e.g.
> create table test (c1 integer);
> ALTER TABLE test SET (toast.autovacuum_enabled = off);
> Why?
1. Why not?
2. They might have toast tables later, after an ALTER ADD COLUMN
for instance.
3. They might have had/needed a toast table in the past. Do
we need to make ALTER DROP COLUMN capable of flushing those
reloptions, so that they won't cause a failure at dump/reload?
I don't see any advantage whatsoever to forbidding this, and
a lot of corner cases to take care of if we did try to forbid it.
regards, tom lane
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
