| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndQuadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: ALTER TABLESPACE ... MOVE ALL TO ... |
| Date: | 2014-01-20 15:46:16 |
| Message-ID: | 14946.1390232776@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Stephen Frost <sfrost(at)snowman(dot)net> writes:
> So you're still looking for an 'OWNED' noise word to be added? Also, I
> did add the ability to specify types of objects (it's often that we'll
> have a "INDEXES" tablespace, so this made sense), so how about:
> ALTER TABLESPACE name MOVE OWNED TO name opt_nowait
> ALTER TABLESPACE name MOVE TABLES OWNED TO name opt_nowait
> ALTER TABLESPACE name MOVE INDEXES OWNED TO name opt_nowait
> ALTER TABLESPACE name MOVE MATERIALIZED VIEWS OWNED TO name opt_nowait
> Removing the 'ALL' entirely?
What if you're a superuser and you want to move everybody's objects
(perhaps in preparation for dropping the tablespace)? I think there's
value in both the ALL and OWNED forms.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simon Riggs | 2014-01-20 15:58:20 | Re: ALTER TABLESPACE ... MOVE ALL TO ... |
| Previous Message | Tom Lane | 2014-01-20 15:22:09 | Re: NOT Null constraint on foreign table not working |