From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: ALTER TABLESPACE MOVE command tag tweak |
Date: | 2014-06-24 02:19:06 |
Message-ID: | 20140624021905.GD5032@eldon.alvh.no-ip.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
> > That it's more-or-less a bulk 'ALTER TABLE' operation is why I had been
> > trying to think of a way to put it under that command. What if we had a
> > more general way to reference 'all objects in a tablespace'?
> > "tablespace.*" or "ALL:TABLESAPCE"? Are there other places which might
> > benefit from being able to take and operate on all objects in a
> > tablespace?
>
> > Of course, we handle this in 'GRANT' with 'GRANT ON ALL TABLES', so why
> > not 'ALTER TABLE ON ALL TABLES IN TABLESPACE <blah>'? that does get
> > pretty darn verbose but is at least a bit more in-line with what we have
> > done before..
>
> That's not a bad line of thought --- I doubt that verbosity is critical
> here.
Yep, that works for my purposes. Also, it seems there should be no
parse conflict because ON is already a reserved keyword ..
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2014-06-24 02:34:38 | Re: [BUGS] BUG #10728: json_to_recordset with nested json objects NULLs columns |
Previous Message | Michael Paquier | 2014-06-24 02:08:18 | Re: [BUGS] BUG #10728: json_to_recordset with nested json objects NULLs columns |