-BEGIN PGP SIGNED MESSAGE-
Hash: RIPEMD160
> As Tom stated it earlier, the ANALYZE slow down is far from being the
> only consequence. The planner will also have more work to do and
> that's the hard point IMHO.
>
> Without studying the impacts of this change on a large set of queries
>
Gregory Stark <[EMAIL PROTECTED]> writes:
> So the syntax would be
> CREATE TABLE foo (..., LIKE bar INCLUDING INDEXES USING INDEX TABLESPACE
> foo_ts, ...)
This (presumably) forces all the indexes into the same tablespace,
so I don't find it to be a complete solution, just a wart.
We could get
"Tom Lane" <[EMAIL PROTECTED]> writes:
> An issue that this patch doesn't address is what happens if the source
> index is in a non-default tablespace that the current user does not have
> CREATE permission for. With both current CVS HEAD and this patch, that
> will result in an error. Is that
