Re: Tablespace issues (comment on ,moving indexes)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Kevin Brown <kevin(at)sysexperts(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Tablespace issues (comment on ,moving indexes)
Date: 2004-08-10 14:03:46
Message-ID: 27904.1092146626@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Kevin Brown <kevin(at)sysexperts(dot)com> writes:
> ... But what we're talking about
> here is brand new functionality for which the language hasn't been
> defined yet.

You're missing the point, which is that there *is* a precedent of long
standing. ALTER TABLE has worked on indexes (and sequences, and views)
for those cases in which the operation sensibly applied for a long time.
In particular, the original 7.1 implementation of ALTER TABLE OWNER
would work on tables, indexes, sequences, and views. Should we really
have insisted on inventing four syntaxes for the identical operation?
Maybe, but we didn't, and now there is a precedent to follow.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-08-10 14:06:31 Re: pg_autovacuum Win32 Service Code
Previous Message pgsql 2004-08-10 13:48:49 Re: fsync vs open_sync (more info)