2014-01-19 02:59:31 +01:00
|
|
|
-- create a tablespace using WITH clause
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLESPACE regress_tblspacewith LOCATION '@testtablespace@' WITH (some_nonexistent_parameter = true); -- fail
|
2014-01-19 02:59:31 +01:00
|
|
|
ERROR: unrecognized parameter "some_nonexistent_parameter"
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLESPACE regress_tblspacewith LOCATION '@testtablespace@' WITH (random_page_cost = 3.0); -- ok
|
2014-01-19 02:59:31 +01:00
|
|
|
-- check to see the parameter was used
|
2016-07-18 00:42:31 +02:00
|
|
|
SELECT spcoptions FROM pg_tablespace WHERE spcname = 'regress_tblspacewith';
|
2014-01-19 02:59:31 +01:00
|
|
|
spcoptions
|
|
|
|
------------------------
|
|
|
|
{random_page_cost=3.0}
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- drop the tablespace so we can re-use the location
|
2016-07-18 00:42:31 +02:00
|
|
|
DROP TABLESPACE regress_tblspacewith;
|
2004-06-18 08:14:31 +02:00
|
|
|
-- create a tablespace we can use
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLESPACE regress_tblspace LOCATION '@testtablespace@';
|
2010-01-05 22:54:00 +01:00
|
|
|
-- try setting and resetting some properties for the new tablespace
|
2017-10-19 14:14:18 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace SET (random_page_cost = 1.0, seq_page_cost = 1.1);
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace SET (some_nonexistent_parameter = true); -- fail
|
2010-01-05 22:54:00 +01:00
|
|
|
ERROR: unrecognized parameter "some_nonexistent_parameter"
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace RESET (random_page_cost = 2.0); -- fail
|
2010-01-05 22:54:00 +01:00
|
|
|
ERROR: RESET must not include values for parameters
|
2017-10-19 14:14:18 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace RESET (random_page_cost, effective_io_concurrency); -- ok
|
2004-11-05 20:17:13 +01:00
|
|
|
-- create a schema we can use
|
|
|
|
CREATE SCHEMA testschema;
|
2004-06-18 08:14:31 +02:00
|
|
|
-- try a table
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLE testschema.foo (i int) TABLESPACE regress_tblspace;
|
2004-06-18 08:14:31 +02:00
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_tablespace t, pg_catalog.pg_class c
|
|
|
|
where c.reltablespace = t.oid AND c.relname = 'foo';
|
2016-07-18 00:42:31 +02:00
|
|
|
relname | spcname
|
|
|
|
---------+------------------
|
|
|
|
foo | regress_tblspace
|
2004-06-18 08:14:31 +02:00
|
|
|
(1 row)
|
|
|
|
|
|
|
|
INSERT INTO testschema.foo VALUES(1);
|
|
|
|
INSERT INTO testschema.foo VALUES(2);
|
2006-02-19 01:04:28 +01:00
|
|
|
-- tables from dynamic sources
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLE testschema.asselect TABLESPACE regress_tblspace AS SELECT 1;
|
2006-02-19 01:04:28 +01:00
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_tablespace t, pg_catalog.pg_class c
|
|
|
|
where c.reltablespace = t.oid AND c.relname = 'asselect';
|
2016-07-18 00:42:31 +02:00
|
|
|
relname | spcname
|
|
|
|
----------+------------------
|
|
|
|
asselect | regress_tblspace
|
2006-02-19 01:04:28 +01:00
|
|
|
(1 row)
|
|
|
|
|
|
|
|
PREPARE selectsource(int) AS SELECT $1;
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLE testschema.asexecute TABLESPACE regress_tblspace
|
2006-02-19 01:04:28 +01:00
|
|
|
AS EXECUTE selectsource(2);
|
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_tablespace t, pg_catalog.pg_class c
|
|
|
|
where c.reltablespace = t.oid AND c.relname = 'asexecute';
|
2016-07-18 00:42:31 +02:00
|
|
|
relname | spcname
|
|
|
|
-----------+------------------
|
|
|
|
asexecute | regress_tblspace
|
2006-02-19 01:04:28 +01:00
|
|
|
(1 row)
|
|
|
|
|
2004-06-18 08:14:31 +02:00
|
|
|
-- index
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE INDEX foo_idx on testschema.foo(i) TABLESPACE regress_tblspace;
|
2004-06-18 08:14:31 +02:00
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_tablespace t, pg_catalog.pg_class c
|
|
|
|
where c.reltablespace = t.oid AND c.relname = 'foo_idx';
|
2016-07-18 00:42:31 +02:00
|
|
|
relname | spcname
|
|
|
|
---------+------------------
|
|
|
|
foo_idx | regress_tblspace
|
2004-06-18 08:14:31 +02:00
|
|
|
(1 row)
|
|
|
|
|
2019-07-23 23:04:21 +02:00
|
|
|
-- check \d output
|
|
|
|
\d testschema.foo
|
|
|
|
Table "testschema.foo"
|
|
|
|
Column | Type | Collation | Nullable | Default
|
|
|
|
--------+---------+-----------+----------+---------
|
|
|
|
i | integer | | |
|
|
|
|
Indexes:
|
|
|
|
"foo_idx" btree (i), tablespace "regress_tblspace"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.foo_idx
|
|
|
|
Index "testschema.foo_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
i | integer | yes | i
|
|
|
|
btree, for table "testschema.foo"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2019-06-07 06:44:17 +02:00
|
|
|
--
|
2018-12-17 19:37:40 +01:00
|
|
|
-- partitioned table
|
2019-06-07 06:44:17 +02:00
|
|
|
--
|
2018-12-17 19:37:40 +01:00
|
|
|
CREATE TABLE testschema.part (a int) PARTITION BY LIST (a);
|
2019-06-07 06:44:17 +02:00
|
|
|
SET default_tablespace TO pg_global;
|
|
|
|
CREATE TABLE testschema.part_1 PARTITION OF testschema.part FOR VALUES IN (1);
|
|
|
|
ERROR: only shared relations can be placed in pg_global tablespace
|
|
|
|
RESET default_tablespace;
|
|
|
|
CREATE TABLE testschema.part_1 PARTITION OF testschema.part FOR VALUES IN (1);
|
|
|
|
SET default_tablespace TO regress_tblspace;
|
|
|
|
CREATE TABLE testschema.part_2 PARTITION OF testschema.part FOR VALUES IN (2);
|
|
|
|
SET default_tablespace TO pg_global;
|
|
|
|
CREATE TABLE testschema.part_3 PARTITION OF testschema.part FOR VALUES IN (3);
|
|
|
|
ERROR: only shared relations can be placed in pg_global tablespace
|
|
|
|
ALTER TABLE testschema.part SET TABLESPACE regress_tblspace;
|
|
|
|
CREATE TABLE testschema.part_3 PARTITION OF testschema.part FOR VALUES IN (3);
|
|
|
|
CREATE TABLE testschema.part_4 PARTITION OF testschema.part FOR VALUES IN (4)
|
|
|
|
TABLESPACE pg_default;
|
|
|
|
CREATE TABLE testschema.part_56 PARTITION OF testschema.part FOR VALUES IN (5, 6)
|
|
|
|
PARTITION BY LIST (a);
|
|
|
|
ALTER TABLE testschema.part SET TABLESPACE pg_default;
|
|
|
|
CREATE TABLE testschema.part_78 PARTITION OF testschema.part FOR VALUES IN (7, 8)
|
|
|
|
PARTITION BY LIST (a);
|
|
|
|
ERROR: only shared relations can be placed in pg_global tablespace
|
|
|
|
CREATE TABLE testschema.part_910 PARTITION OF testschema.part FOR VALUES IN (9, 10)
|
|
|
|
PARTITION BY LIST (a) TABLESPACE regress_tblspace;
|
|
|
|
RESET default_tablespace;
|
|
|
|
CREATE TABLE testschema.part_78 PARTITION OF testschema.part FOR VALUES IN (7, 8)
|
|
|
|
PARTITION BY LIST (a);
|
2018-12-17 19:37:40 +01:00
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_class c
|
2019-06-07 06:44:17 +02:00
|
|
|
JOIN pg_catalog.pg_namespace n ON (c.relnamespace = n.oid)
|
2018-12-17 19:37:40 +01:00
|
|
|
LEFT JOIN pg_catalog.pg_tablespace t ON c.reltablespace = t.oid
|
2019-06-07 06:44:17 +02:00
|
|
|
where c.relname LIKE 'part%' AND n.nspname = 'testschema' order by relname;
|
2018-12-17 19:37:40 +01:00
|
|
|
relname | spcname
|
|
|
|
----------+------------------
|
|
|
|
part |
|
2019-06-07 06:44:17 +02:00
|
|
|
part_1 |
|
|
|
|
part_2 | regress_tblspace
|
|
|
|
part_3 | regress_tblspace
|
|
|
|
part_4 |
|
|
|
|
part_56 | regress_tblspace
|
|
|
|
part_78 |
|
|
|
|
part_910 | regress_tblspace
|
|
|
|
(8 rows)
|
2018-12-17 19:37:40 +01:00
|
|
|
|
2019-06-07 06:44:17 +02:00
|
|
|
RESET default_tablespace;
|
2018-12-17 19:37:40 +01:00
|
|
|
DROP TABLE testschema.part;
|
2018-11-03 17:23:40 +01:00
|
|
|
-- partitioned index
|
|
|
|
CREATE TABLE testschema.part (a int) PARTITION BY LIST (a);
|
|
|
|
CREATE TABLE testschema.part1 PARTITION OF testschema.part FOR VALUES IN (1);
|
|
|
|
CREATE INDEX part_a_idx ON testschema.part (a) TABLESPACE regress_tblspace;
|
|
|
|
CREATE TABLE testschema.part2 PARTITION OF testschema.part FOR VALUES IN (2);
|
|
|
|
SELECT relname, spcname FROM pg_catalog.pg_tablespace t, pg_catalog.pg_class c
|
|
|
|
where c.reltablespace = t.oid AND c.relname LIKE 'part%_idx';
|
|
|
|
relname | spcname
|
|
|
|
-------------+------------------
|
|
|
|
part1_a_idx | regress_tblspace
|
|
|
|
part2_a_idx | regress_tblspace
|
|
|
|
part_a_idx | regress_tblspace
|
|
|
|
(3 rows)
|
|
|
|
|
2019-07-23 23:04:21 +02:00
|
|
|
\d testschema.part
|
|
|
|
Partitioned table "testschema.part"
|
|
|
|
Column | Type | Collation | Nullable | Default
|
|
|
|
--------+---------+-----------+----------+---------
|
|
|
|
a | integer | | |
|
|
|
|
Partition key: LIST (a)
|
|
|
|
Indexes:
|
|
|
|
"part_a_idx" btree (a), tablespace "regress_tblspace"
|
|
|
|
Number of partitions: 2 (Use \d+ to list them.)
|
|
|
|
|
|
|
|
\d+ testschema.part
|
|
|
|
Partitioned table "testschema.part"
|
|
|
|
Column | Type | Collation | Nullable | Default | Storage | Stats target | Description
|
|
|
|
--------+---------+-----------+----------+---------+---------+--------------+-------------
|
|
|
|
a | integer | | | | plain | |
|
|
|
|
Partition key: LIST (a)
|
|
|
|
Indexes:
|
|
|
|
"part_a_idx" btree (a), tablespace "regress_tblspace"
|
|
|
|
Partitions: testschema.part1 FOR VALUES IN (1),
|
|
|
|
testschema.part2 FOR VALUES IN (2)
|
|
|
|
|
|
|
|
\d testschema.part1
|
|
|
|
Table "testschema.part1"
|
|
|
|
Column | Type | Collation | Nullable | Default
|
|
|
|
--------+---------+-----------+----------+---------
|
|
|
|
a | integer | | |
|
|
|
|
Partition of: testschema.part FOR VALUES IN (1)
|
|
|
|
Indexes:
|
|
|
|
"part1_a_idx" btree (a), tablespace "regress_tblspace"
|
|
|
|
|
|
|
|
\d+ testschema.part1
|
|
|
|
Table "testschema.part1"
|
|
|
|
Column | Type | Collation | Nullable | Default | Storage | Stats target | Description
|
|
|
|
--------+---------+-----------+----------+---------+---------+--------------+-------------
|
|
|
|
a | integer | | | | plain | |
|
|
|
|
Partition of: testschema.part FOR VALUES IN (1)
|
|
|
|
Partition constraint: ((a IS NOT NULL) AND (a = 1))
|
|
|
|
Indexes:
|
|
|
|
"part1_a_idx" btree (a), tablespace "regress_tblspace"
|
|
|
|
|
2019-04-18 00:17:43 +02:00
|
|
|
\d testschema.part_a_idx
|
|
|
|
Partitioned index "testschema.part_a_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
a | integer | yes | a
|
|
|
|
btree, for table "testschema.part"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 2 (Use \d+ to list them.)
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d+ testschema.part_a_idx
|
|
|
|
Partitioned index "testschema.part_a_idx"
|
|
|
|
Column | Type | Key? | Definition | Storage | Stats target
|
|
|
|
--------+---------+------+------------+---------+--------------
|
|
|
|
a | integer | yes | a | plain |
|
|
|
|
btree, for table "testschema.part"
|
|
|
|
Partitions: testschema.part1_a_idx,
|
|
|
|
testschema.part2_a_idx
|
2019-04-18 00:17:43 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
-- partitioned rels cannot specify the default tablespace. These fail:
|
|
|
|
CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE pg_default;
|
|
|
|
ERROR: cannot specify default tablespace for partitioned relations
|
|
|
|
CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE pg_default) PARTITION BY LIST (a);
|
2019-04-30 16:00:38 +02:00
|
|
|
ERROR: cannot specify default tablespace for partitioned relations
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
SET default_tablespace TO 'pg_default';
|
|
|
|
CREATE TABLE testschema.dflt (a int PRIMARY KEY) PARTITION BY LIST (a) TABLESPACE regress_tblspace;
|
|
|
|
ERROR: cannot specify default tablespace for partitioned relations
|
|
|
|
CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE regress_tblspace) PARTITION BY LIST (a);
|
|
|
|
ERROR: cannot specify default tablespace for partitioned relations
|
|
|
|
-- but these work:
|
|
|
|
CREATE TABLE testschema.dflt (a int PRIMARY KEY USING INDEX TABLESPACE regress_tblspace) PARTITION BY LIST (a) TABLESPACE regress_tblspace;
|
|
|
|
SET default_tablespace TO '';
|
|
|
|
CREATE TABLE testschema.dflt2 (a int PRIMARY KEY) PARTITION BY LIST (a);
|
|
|
|
DROP TABLE testschema.dflt, testschema.dflt2;
|
2016-11-23 19:45:55 +01:00
|
|
|
-- check that default_tablespace doesn't affect ALTER TABLE index rebuilds
|
|
|
|
CREATE TABLE testschema.test_default_tab(id bigint) TABLESPACE regress_tblspace;
|
|
|
|
INSERT INTO testschema.test_default_tab VALUES (1);
|
|
|
|
CREATE INDEX test_index1 on testschema.test_default_tab (id);
|
|
|
|
CREATE INDEX test_index2 on testschema.test_default_tab (id) TABLESPACE regress_tblspace;
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
ALTER TABLE testschema.test_default_tab ADD CONSTRAINT test_index3 PRIMARY KEY (id);
|
|
|
|
ALTER TABLE testschema.test_default_tab ADD CONSTRAINT test_index4 UNIQUE (id) USING INDEX TABLESPACE regress_tblspace;
|
2016-11-23 19:45:55 +01:00
|
|
|
\d testschema.test_index1
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index2
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
\d testschema.test_index3
|
|
|
|
Index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2016-11-23 19:45:55 +01:00
|
|
|
-- use a custom tablespace for default_tablespace
|
|
|
|
SET default_tablespace TO regress_tblspace;
|
|
|
|
-- tablespace should not change if no rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab ALTER id TYPE bigint;
|
|
|
|
\d testschema.test_index1
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index2
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
\d testschema.test_index3
|
|
|
|
Index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2016-11-23 19:45:55 +01:00
|
|
|
SELECT * FROM testschema.test_default_tab;
|
|
|
|
id
|
|
|
|
----
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- tablespace should not change even if there is an index rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab ALTER id TYPE int;
|
|
|
|
\d testschema.test_index1
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index2
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
\d testschema.test_index3
|
|
|
|
Index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2016-11-23 19:45:55 +01:00
|
|
|
SELECT * FROM testschema.test_default_tab;
|
|
|
|
id
|
|
|
|
----
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- now use the default tablespace for default_tablespace
|
|
|
|
SET default_tablespace TO '';
|
|
|
|
-- tablespace should not change if no rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab ALTER id TYPE int;
|
|
|
|
\d testschema.test_index1
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index2
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
\d testschema.test_index3
|
|
|
|
Index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2016-11-23 19:45:55 +01:00
|
|
|
-- tablespace should not change even if there is an index rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab ALTER id TYPE bigint;
|
|
|
|
\d testschema.test_index1
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index2
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
2016-11-23 19:45:55 +01:00
|
|
|
btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
\d testschema.test_index3
|
|
|
|
Index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab"
|
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
2016-11-23 19:45:55 +01:00
|
|
|
DROP TABLE testschema.test_default_tab;
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
-- check that default_tablespace doesn't affect ALTER TABLE index rebuilds
|
|
|
|
-- (this time with a partitioned table)
|
|
|
|
CREATE TABLE testschema.test_default_tab_p(id bigint, val bigint)
|
|
|
|
PARTITION BY LIST (id) TABLESPACE regress_tblspace;
|
|
|
|
CREATE TABLE testschema.test_default_tab_p1 PARTITION OF testschema.test_default_tab_p
|
|
|
|
FOR VALUES IN (1);
|
|
|
|
INSERT INTO testschema.test_default_tab_p VALUES (1);
|
|
|
|
CREATE INDEX test_index1 on testschema.test_default_tab_p (val);
|
|
|
|
CREATE INDEX test_index2 on testschema.test_default_tab_p (val) TABLESPACE regress_tblspace;
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ADD CONSTRAINT test_index3 PRIMARY KEY (id);
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ADD CONSTRAINT test_index4 UNIQUE (id) USING INDEX TABLESPACE regress_tblspace;
|
|
|
|
\d testschema.test_index1
|
|
|
|
Partitioned index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index2
|
|
|
|
Partitioned index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_index3
|
|
|
|
Partitioned index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Partitioned index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
-- use a custom tablespace for default_tablespace
|
|
|
|
SET default_tablespace TO regress_tblspace;
|
|
|
|
-- tablespace should not change if no rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ALTER val TYPE bigint;
|
|
|
|
\d testschema.test_index1
|
|
|
|
Partitioned index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index2
|
|
|
|
Partitioned index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_index3
|
|
|
|
Partitioned index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Partitioned index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
SELECT * FROM testschema.test_default_tab_p;
|
|
|
|
id | val
|
|
|
|
----+-----
|
|
|
|
1 |
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- tablespace should not change even if there is an index rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ALTER val TYPE int;
|
|
|
|
\d testschema.test_index1
|
|
|
|
Partitioned index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
val | integer | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index2
|
|
|
|
Partitioned index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
val | integer | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_index3
|
|
|
|
Partitioned index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Partitioned index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
SELECT * FROM testschema.test_default_tab_p;
|
|
|
|
id | val
|
|
|
|
----+-----
|
|
|
|
1 |
|
|
|
|
(1 row)
|
|
|
|
|
|
|
|
-- now use the default tablespace for default_tablespace
|
|
|
|
SET default_tablespace TO '';
|
|
|
|
-- tablespace should not change if no rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ALTER val TYPE int;
|
|
|
|
\d testschema.test_index1
|
|
|
|
Partitioned index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
val | integer | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index2
|
|
|
|
Partitioned index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
val | integer | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_index3
|
|
|
|
Partitioned index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Partitioned index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
-- tablespace should not change even if there is an index rewrite
|
|
|
|
ALTER TABLE testschema.test_default_tab_p ALTER val TYPE bigint;
|
|
|
|
\d testschema.test_index1
|
|
|
|
Partitioned index "testschema.test_index1"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index2
|
|
|
|
Partitioned index "testschema.test_index2"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
val | bigint | yes | val
|
|
|
|
btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_index3
|
|
|
|
Partitioned index "testschema.test_index3"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
primary key, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
|
|
|
|
\d testschema.test_index4
|
|
|
|
Partitioned index "testschema.test_index4"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
id | bigint | yes | id
|
|
|
|
unique, btree, for table "testschema.test_default_tab_p"
|
2019-07-23 23:04:21 +02:00
|
|
|
Number of partitions: 1 (Use \d+ to list them.)
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
DROP TABLE testschema.test_default_tab_p;
|
2016-11-24 20:13:19 +01:00
|
|
|
-- check that default_tablespace affects index additions in ALTER TABLE
|
|
|
|
CREATE TABLE testschema.test_tab(id int) TABLESPACE regress_tblspace;
|
|
|
|
INSERT INTO testschema.test_tab VALUES (1);
|
|
|
|
SET default_tablespace TO regress_tblspace;
|
|
|
|
ALTER TABLE testschema.test_tab ADD CONSTRAINT test_tab_unique UNIQUE (id);
|
|
|
|
SET default_tablespace TO '';
|
|
|
|
ALTER TABLE testschema.test_tab ADD CONSTRAINT test_tab_pkey PRIMARY KEY (id);
|
|
|
|
\d testschema.test_tab_unique
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_tab_unique"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-24 20:13:19 +01:00
|
|
|
unique, btree, for table "testschema.test_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_tab_pkey
|
2018-07-19 20:53:41 +02:00
|
|
|
Index "testschema.test_tab_pkey"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
id | integer | yes | id
|
2016-11-24 20:13:19 +01:00
|
|
|
primary key, btree, for table "testschema.test_tab"
|
|
|
|
|
|
|
|
SELECT * FROM testschema.test_tab;
|
|
|
|
id
|
|
|
|
----
|
|
|
|
1
|
|
|
|
(1 row)
|
|
|
|
|
Fix tablespace inheritance for partitioned rels
Commit ca4103025dfe left a few loose ends. The most important one
(broken pg_dump output) is already fixed by virtue of commit
3b23552ad8bb, but some things remained:
* When ALTER TABLE rewrites tables, the indexes must remain in the
tablespace they were originally in. This didn't work because
index recreation during ALTER TABLE runs manufactured SQL (yuck),
which runs afoul of default_tablespace in competition with the parent
relation tablespace. To fix, reset default_tablespace to the empty
string temporarily, and add the TABLESPACE clause as appropriate.
* Setting a partitioned rel's tablespace to the database default is
confusing; if it worked, it would direct the partitions to that
tablespace regardless of default_tablespace. But in reality it does
not work, and making it work is a larger project. Therefore, throw
an error when this condition is detected, to alert the unwary.
Add some docs and tests, too.
Author: Álvaro Herrera
Discussion: https://postgr.es/m/CAKJS1f_1c260nOt_vBJ067AZ3JXptXVRohDVMLEBmudX1YEx-A@mail.gmail.com
2019-04-25 16:20:23 +02:00
|
|
|
DROP TABLE testschema.test_tab;
|
|
|
|
-- check that default_tablespace is handled correctly by multi-command
|
|
|
|
-- ALTER TABLE that includes a tablespace-preserving rewrite
|
|
|
|
CREATE TABLE testschema.test_tab(a int, b int, c int);
|
|
|
|
SET default_tablespace TO regress_tblspace;
|
|
|
|
ALTER TABLE testschema.test_tab ADD CONSTRAINT test_tab_unique UNIQUE (a);
|
|
|
|
CREATE INDEX test_tab_a_idx ON testschema.test_tab (a);
|
|
|
|
SET default_tablespace TO '';
|
|
|
|
CREATE INDEX test_tab_b_idx ON testschema.test_tab (b);
|
|
|
|
\d testschema.test_tab_unique
|
|
|
|
Index "testschema.test_tab_unique"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
a | integer | yes | a
|
|
|
|
unique, btree, for table "testschema.test_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_tab_a_idx
|
|
|
|
Index "testschema.test_tab_a_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
a | integer | yes | a
|
|
|
|
btree, for table "testschema.test_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_tab_b_idx
|
|
|
|
Index "testschema.test_tab_b_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
b | integer | yes | b
|
|
|
|
btree, for table "testschema.test_tab"
|
|
|
|
|
|
|
|
ALTER TABLE testschema.test_tab ALTER b TYPE bigint, ADD UNIQUE (c);
|
|
|
|
\d testschema.test_tab_unique
|
|
|
|
Index "testschema.test_tab_unique"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
a | integer | yes | a
|
|
|
|
unique, btree, for table "testschema.test_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_tab_a_idx
|
|
|
|
Index "testschema.test_tab_a_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+---------+------+------------
|
|
|
|
a | integer | yes | a
|
|
|
|
btree, for table "testschema.test_tab"
|
|
|
|
Tablespace: "regress_tblspace"
|
|
|
|
|
|
|
|
\d testschema.test_tab_b_idx
|
|
|
|
Index "testschema.test_tab_b_idx"
|
|
|
|
Column | Type | Key? | Definition
|
|
|
|
--------+--------+------+------------
|
|
|
|
b | bigint | yes | b
|
|
|
|
btree, for table "testschema.test_tab"
|
|
|
|
|
2016-11-24 20:13:19 +01:00
|
|
|
DROP TABLE testschema.test_tab;
|
2007-01-02 22:43:36 +01:00
|
|
|
-- let's try moving a table from one place to another
|
|
|
|
CREATE TABLE testschema.atable AS VALUES (1), (2);
|
|
|
|
CREATE UNIQUE INDEX anindex ON testschema.atable(column1);
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLE testschema.atable SET TABLESPACE regress_tblspace;
|
|
|
|
ALTER INDEX testschema.anindex SET TABLESPACE regress_tblspace;
|
2018-11-23 12:44:15 +01:00
|
|
|
ALTER INDEX testschema.part_a_idx SET TABLESPACE pg_global;
|
|
|
|
ERROR: only shared relations can be placed in pg_global tablespace
|
2018-11-03 17:23:40 +01:00
|
|
|
ALTER INDEX testschema.part_a_idx SET TABLESPACE pg_default;
|
|
|
|
ALTER INDEX testschema.part_a_idx SET TABLESPACE regress_tblspace;
|
2007-01-02 22:43:36 +01:00
|
|
|
INSERT INTO testschema.atable VALUES(3); -- ok
|
|
|
|
INSERT INTO testschema.atable VALUES(1); -- fail (checks index)
|
2007-06-04 00:16:03 +02:00
|
|
|
ERROR: duplicate key value violates unique constraint "anindex"
|
2009-08-01 21:59:41 +02:00
|
|
|
DETAIL: Key (column1)=(1) already exists.
|
2007-01-02 22:43:36 +01:00
|
|
|
SELECT COUNT(*) FROM testschema.atable; -- checks heap
|
|
|
|
count
|
|
|
|
-------
|
|
|
|
3
|
|
|
|
(1 row)
|
|
|
|
|
2004-06-18 08:14:31 +02:00
|
|
|
-- Will fail with bad path
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLESPACE regress_badspace LOCATION '/no/such/location';
|
2010-01-12 03:42:52 +01:00
|
|
|
ERROR: directory "/no/such/location" does not exist
|
2004-06-18 08:14:31 +02:00
|
|
|
-- No such tablespace
|
2016-07-18 00:42:31 +02:00
|
|
|
CREATE TABLE bar (i int) TABLESPACE regress_nosuchspace;
|
|
|
|
ERROR: tablespace "regress_nosuchspace" does not exist
|
2004-06-18 08:14:31 +02:00
|
|
|
-- Fail, not empty
|
2016-07-18 00:42:31 +02:00
|
|
|
DROP TABLESPACE regress_tblspace;
|
|
|
|
ERROR: tablespace "regress_tblspace" is not empty
|
|
|
|
CREATE ROLE regress_tablespace_user1 login;
|
|
|
|
CREATE ROLE regress_tablespace_user2 login;
|
2017-02-12 22:03:41 +01:00
|
|
|
GRANT USAGE ON SCHEMA testschema TO regress_tablespace_user2;
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace OWNER TO regress_tablespace_user1;
|
2017-02-12 22:03:41 +01:00
|
|
|
CREATE TABLE testschema.tablespace_acl (c int);
|
|
|
|
-- new owner lacks permission to create this index from scratch
|
|
|
|
CREATE INDEX k ON testschema.tablespace_acl (c) TABLESPACE regress_tblspace;
|
|
|
|
ALTER TABLE testschema.tablespace_acl OWNER TO regress_tablespace_user2;
|
2016-07-18 00:42:31 +02:00
|
|
|
SET SESSION ROLE regress_tablespace_user2;
|
|
|
|
CREATE TABLE tablespace_table (i int) TABLESPACE regress_tblspace; -- fail
|
|
|
|
ERROR: permission denied for tablespace regress_tblspace
|
2017-02-12 22:03:41 +01:00
|
|
|
ALTER TABLE testschema.tablespace_acl ALTER c TYPE bigint;
|
2014-11-12 13:33:17 +01:00
|
|
|
RESET ROLE;
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLESPACE regress_tblspace RENAME TO regress_tblspace_renamed;
|
|
|
|
ALTER TABLE ALL IN TABLESPACE regress_tblspace_renamed SET TABLESPACE pg_default;
|
|
|
|
ALTER INDEX ALL IN TABLESPACE regress_tblspace_renamed SET TABLESPACE pg_default;
|
2014-01-19 00:56:40 +01:00
|
|
|
-- Should show notice that nothing was done
|
2016-07-18 00:42:31 +02:00
|
|
|
ALTER TABLE ALL IN TABLESPACE regress_tblspace_renamed SET TABLESPACE pg_default;
|
|
|
|
NOTICE: no matching relations in tablespace "regress_tblspace_renamed" found
|
2014-01-19 00:56:40 +01:00
|
|
|
-- Should succeed
|
2016-07-18 00:42:31 +02:00
|
|
|
DROP TABLESPACE regress_tblspace_renamed;
|
2004-06-18 08:14:31 +02:00
|
|
|
DROP SCHEMA testschema CASCADE;
|
2018-11-03 17:23:40 +01:00
|
|
|
NOTICE: drop cascades to 6 other objects
|
2008-06-11 23:53:49 +02:00
|
|
|
DETAIL: drop cascades to table testschema.foo
|
|
|
|
drop cascades to table testschema.asselect
|
|
|
|
drop cascades to table testschema.asexecute
|
2018-11-03 17:23:40 +01:00
|
|
|
drop cascades to table testschema.part
|
2008-06-11 23:53:49 +02:00
|
|
|
drop cascades to table testschema.atable
|
2017-02-12 22:03:41 +01:00
|
|
|
drop cascades to table testschema.tablespace_acl
|
2016-07-18 00:42:31 +02:00
|
|
|
DROP ROLE regress_tablespace_user1;
|
|
|
|
DROP ROLE regress_tablespace_user2;
|