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 okay?
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 the
Attached is a proposed patch for bug #3921, which complained that CREATE
TABLE LIKE INCLUDING INDEXES fails inappropriately for non-superusers.
There are two parts to the patch: the first follows Greg Starks' opinion
that explicitly specifying the current database's default tablespace
shouldn't
