Simon Riggs wrote:
> Why do we protect against this?
>
> postgres=# alter table test set (nonexistent = on);
> ERROR: unrecognized parameter "notexistent"
Eh? The parameter doesn't exist. It's not exactly the same as defining
a value for a parameter that exists but is unused.
--
Alvaro Herr
Simon Riggs wrote:
> Also, this seems not to work?
>
> postgres=# alter table test set (my.expectation = on);
> ERROR: unrecognized parameter namespace "my"
>
> I thought we had enabled custom table options in this release?
> Or was that deferred, or even rejected completely?
IIRC you can defi
On Wed, 2010-04-28 at 21:11 -0400, Tom Lane wrote:
> Simon Riggs 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 no
Simon Riggs 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
fo
