Simon Riggs <simon(at)2ndQuadrant(dot)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);
1. Why not?
2. They might have toast tables later, after an ALTER ADD COLUMN
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
In response to
pgsql-hackers by date
|Next:||From: Tom Lane||Date: 2010-04-29 01:15:00|
|Subject: Re: Add column if not exists (CINE) |
|Previous:||From: Robert Haas||Date: 2010-04-29 00:46:27|
|Subject: Re: Add column if not exists (CINE)|