On Fri, 2014-05-09 at 17:16 -0400, Stephen Frost wrote:
Guillaume,
* Guillaume Lelarge (guilla...@lelarge.info) wrote:
Should information_schema tables be moved and not pg_catalog ones? it
doesn't seem consistent to me.
The catalog tables are moved by changing the database's tablespace,
* Guillaume Lelarge (guilla...@lelarge.info) wrote:
Thanks for the explanation. I should have RTFM before complaining. Sorry
for the noise :)
No prob. If people don't feel that makes sense then we can still change
it.. I don't feel particularly strongly either way, though I seem to
recall my
Hey,
I was working on adding support to the new MOVE clause of the ALTER
TABLESPACE statement to pgAdmin when I noticed this issue. See this
example:
Fresh git compilation, and new database on a new cluster:
$ createdb b1
$ psql b1
psql (9.4devel)
Type help for help.
b1=# CREATE TABLESPACE ts1
Guillaume,
* Guillaume Lelarge (guilla...@lelarge.info) wrote:
Should information_schema tables be moved and not pg_catalog ones? it
doesn't seem consistent to me.
The catalog tables are moved by changing the database's tablespace, eg:
ALTER DATABASE ... SET TABLESPACE
That also moves any
