Skip to content

G
Gpdb

Greenplum / Gpdb

通知 7
Star 1
Fork 0
G
Gpdb

体验新版 GitCode，发现更多精彩内容 >>

提交 ce2dab7f 编写于 作者: M Mel Kiyama 提交者： David Yozie
浏览文件
操作

docs - CREATE TABLESPACE command (#6007) 

* docs - CREATE TABLESPACE command

--removed filespace information
--added per segment location syntax
--added function gp_tablespace_location()

GPDB 6.0 ONLY.

NOTE: Does not include topics in Admin Guide.
Assigning a tablespace for temp files currently does not work.

* docs - removed references to filespace.

* Small line edit

* Line edit

* line edit

* correct my own typo

* PostgreSQL -> Greenplum Database

* line edits
上级 a973f5fe
隐藏空白更改
内联 并排
Showing with 234 addition and 83 deletion
gpdb-doc/dita/ref_guide/feature_summary.xml
浏览文件 @ ce2dab7f
......@@ -207,9 +207,9 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
Database system, some SQL commands have been added or modified, and there are a few
PostgreSQL features that are not supported. Greenplum has also added features not found in
PostgreSQL, such as physical data distribution, parallel query optimization, external
tables, resource queues, and enhanced table partitioning. For full
SQL syntax and references, see the <xref href="sql_commands/sql_ref.xml#topic1" type="topic"
format="dita"/>.</p>
tables, resource queues, and enhanced table partitioning. For full SQL syntax and
references, see the <xref href="sql_commands/sql_ref.xml#topic1" type="topic" format="dita"
/>.</p>
<table id="ik213423">
<title>SQL Support in Greenplum Database</title>
<tgroup cols="3">
......@@ -250,12 +250,6 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<entry colname="col3">Changes the definition of a Greenplum Database extension - based
on PostgreSQL 9.6. </entry>
</row>
<row>
<entry colname="col1"><codeph>ALTER FILESPACE</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3">Greenplum Database parallel tablespace feature - not in
PostgreSQL 8.3.</entry>
</row>
<row>
<entry colname="col1"><codeph>ALTER FUNCTION</codeph></entry>
<entry colname="col2">YES</entry>
......@@ -342,7 +336,8 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<row>
<entry colname="col1"><codeph>ALTER TYPE</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p><codeph>SET DEFAULT ENCODING</codeph></p></entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p><codeph>SET DEFAULT
ENCODING</codeph></p></entry>
</row>
<row>
<entry colname="col1"><codeph>ALTER USER</codeph></entry>
......@@ -440,7 +435,7 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<row>
<entry colname="col1"><codeph>CREATE EXTENSION</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3">Loads a new extension into Greenplum Database - based on
<entry colname="col3">Loads a new extension into Greenplum Database - based on
PostgreSQL 9.6.</entry>
</row>
<row>
......@@ -529,8 +524,8 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<entry colname="col2">YES</entry>
<entry colname="col3"><b>Limitations:</b><p>The <codeph>lastval()</codeph> and
<codeph>currval()</codeph> functions are not supported.</p><p>The
<codeph>setval()</codeph> function is only allowed in queries that do not operate
on distributed data.</p></entry>
<codeph>setval()</codeph> function is only allowed in queries that do not
operate on distributed data.</p></entry>
</row>
<row>
<entry colname="col1"><codeph>CREATE TABLE</codeph></entry>
......@@ -558,9 +553,10 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
</row>
<row>
<entry colname="col1"><codeph>CREATE TABLESPACE</codeph></entry>
<entry colname="col2"><b otherprops="red">NO</b></entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p><codeph>FILESPACE
</codeph><i>filespace_name</i></p></entry>
<entry colname="col2"><b otherprops="red">YES</b></entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p>Specify host file system
locations for specific segment instances.</p><p><codeph>WITH
(content<varname>ID_1</varname>='<varname>/path/to/dir1</varname>...)</codeph></p></entry>
</row>
<row>
<entry colname="col1"><codeph>CREATE TRIGGER</codeph></entry>
......@@ -570,8 +566,10 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<row>
<entry colname="col1"><codeph>CREATE TYPE</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p><codeph>COMPRESSTYPE | COMPRESSLEVEL | BLOCKSIZE</codeph></p><p><b>Limitations:</b></p><p>The functions used to implement a new base
type must be <codeph>IMMUTABLE</codeph> functions.</p></entry>
<entry colname="col3"><b>Greenplum Database Clauses:</b><p><codeph>COMPRESSTYPE |
COMPRESSLEVEL | BLOCKSIZE</codeph></p><p><b>Limitations:</b></p><p>The functions
used to implement a new base type must be <codeph>IMMUTABLE</codeph>
functions.</p></entry>
</row>
<row>
<entry colname="col1"><codeph>CREATE USER</codeph></entry>
......@@ -650,12 +648,6 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<entry colname="col3">Greenplum Database parallel ETL feature - not in PostgreSQL
8.3.</entry>
</row>
<row>
<entry colname="col1"><codeph>DROP FILESPACE</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3">Greenplum Database parallel tablespace feature - not in
PostgreSQL 8.3.</entry>
</row>
<row>
<entry colname="col1"><codeph>DROP FUNCTION</codeph></entry>
<entry colname="col2">YES</entry>
......@@ -735,7 +727,7 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
</row>
<row>
<entry colname="col1"><codeph>DROP TABLESPACE</codeph></entry>
<entry colname="col2"><b otherprops="red">NO</b></entry>
<entry colname="col2">YES</entry>
<entry colname="col3"/>
</row>
<row>
......@@ -942,8 +934,8 @@ NEXT 10 ROWS ONLY; </codeblock><p>Greenplum
<row>
<entry colname="col1"><codeph>UPDATE</codeph></entry>
<entry colname="col2">YES</entry>
<entry colname="col3"><b>Limitations:</b><p><codeph>SET</codeph>
not allowed for Greenplum distribution key columns.</p></entry>
<entry colname="col3"><b>Limitations:</b><p><codeph>SET</codeph> not allowed for
Greenplum distribution key columns.</p></entry>
</row>
<row>
<entry colname="col1"><codeph>VACUUM</codeph></entry>
......
gpdb-doc/dita/ref_guide/sql_commands/COMMENT.xml
浏览文件 @ ce2dab7f
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic id="topic1"><title id="bi20941">COMMENT</title><body><p id="sql_command_desc">Defines or change the comment of an object.</p><section id="section2"><title>Synopsis</title><codeblock id="sql_command_synopsis">COMMENT ON
<topic id="topic1">
<title id="bi20941">COMMENT</title>
<body>
<p id="sql_command_desc">Defines or changes the comment of an object.</p>
<section id="section2">
<title>Synopsis</title>
<codeblock id="sql_command_synopsis">COMMENT ON
{ TABLE <varname>object_name</varname> |
COLUMN <varname>table_name.column_name</varname> |
AGGREGATE <varname>agg_name</varname> (<varname>agg_type</varname> [, ...]) |
......@@ -12,7 +18,6 @@
DOMAIN <varname>object_name</varname> |
FOREIGN DATA WRAPPER <varname>object_name</varname> |
FOREIGN TABLE <varname>object_name</varname> |
  FILESPACE <varname>object_name</varname> |
FUNCTION <varname>func_name</varname> ([[<varname>argmode</varname>] [<varname>argname</varname>] <varname>argtype</varname> [, ...]]) |
INDEX <varname>object_name</varname> |
LARGE OBJECT <varname>large_object_oid</varname> |
......@@ -30,33 +35,106 @@
TRIGGER <varname>trigger_name</varname> ON <varname>table_name</varname> |
TYPE <varname>object_name</varname> |
VIEW <varname>object_name</varname> }
IS '<varname>text</varname>'</codeblock></section><section id="section3"><title>Description</title><p><codeph>COMMENT</codeph> stores a comment about a database object. To
modify a comment, issue a new <codeph>COMMENT</codeph> command for the
same object. Only one comment string is stored for each object. To remove
a comment, write <codeph>NULL</codeph> in place of the text string. Comments
are automatically dropped when the object is dropped.</p><p>Comments can be easily retrieved with the psql meta-commands <codeph>\dd</codeph>,
<codeph>\d+</codeph>, and <codeph>\l+</codeph>. Other user interfaces
to retrieve comments can be built atop the same built-in functions that
psql uses, namely <codeph>obj_description</codeph>, <codeph>col_description</codeph>,
and <codeph>shobj_description</codeph>.</p></section><section id="section4"><title>Parameters</title><parml><plentry><pt><varname>object_name</varname></pt><pt><varname>table_name.column_name</varname></pt><pt><varname>agg_name</varname></pt><pt><varname>constraint_name</varname></pt><pt><varname>func_name</varname></pt><pt><varname>op</varname></pt><pt><varname>rule_name</varname></pt><pt><varname>trigger_name</varname></pt><pd>The name of the object to be commented. Names of tables, aggregates,
domains, foreign tables, functions, indexes, operators, operator classes, sequences,
types, and views may be schema-qualified. <note>Greenplum Database does not support triggers.</note></pd></plentry><plentry><pt><varname>agg_type</varname></pt><pd>An input data type on which the aggregate function operates. To reference
a zero-argument aggregate function, write <codeph>*</codeph> in place
of the list of input data types. </pd></plentry><plentry><pt><varname>sourcetype</varname></pt><pd>The name of the source data type of the cast. </pd></plentry><plentry><pt><varname>targettype</varname></pt><pd>The name of the target data type of the cast. </pd></plentry><plentry><pt><varname>argmode</varname></pt><pd>The mode of a function argument: either <codeph>IN</codeph>, <codeph>OUT</codeph>,
<codeph>INOUT</codeph>, or <codeph>VARIADIC</codeph>. If omitted, the default is <codeph>IN</codeph>.
Note that <codeph>COMMENT ON FUNCTION</codeph> does not actually pay
any attention to <codeph>OUT</codeph> arguments, since only the input
arguments are needed to determine the function's identity. So it is
sufficient to list the <codeph>IN</codeph>, <codeph>INOUT</codeph>, and <codeph>VARIADIC</codeph>
arguments. </pd></plentry><plentry><pt><varname>argname</varname></pt><pd>The name of a function argument. Note that <codeph>COMMENT ON FUNCTION</codeph>
does not actually pay any attention to argument names, since only the
argument data types are needed to determine the function's identity.
</pd></plentry><plentry><pt><varname>argtype</varname></pt><pd>The data type(s) of the function's arguments (optionally schema-qualified),
if any. </pd></plentry><plentry><pt><varname>large_object_oid</varname></pt><pd>The OID of the large object. </pd></plentry><plentry><pt>PROCEDURAL</pt><pd>This is a noise word. </pd></plentry><plentry><pt><varname>text</varname></pt><pd>The new comment, written as a string literal; or <codeph>NULL</codeph>
to drop the comment.</pd></plentry></parml></section><section id="section5"><title>Notes</title><p>There is presently no security mechanism for comments: any user connected
to a database can see all the comments for objects in that database (although
only superusers can change comments for objects that they do not own).
For shared objects such as databases, roles, and tablespaces comments
are stored globally and any user connected to any database can see all
the comments for shared objects. Therefore, do not put security-critical
information in comments.</p></section><section id="section6"><title>Examples</title><p>Attach a comment to the table <codeph>mytable</codeph>: </p><codeblock>COMMENT ON TABLE mytable IS 'This is my table.';</codeblock><p>Remove it again: </p><codeblock>COMMENT ON TABLE mytable IS NULL;</codeblock></section><section id="section7"><title>Compatibility</title><p>There is no <codeph>COMMENT</codeph> statement in the SQL standard.</p></section></body></topic>
IS '<varname>text</varname>'</codeblock>
</section>
<section id="section3">
<title>Description</title>
<p><codeph>COMMENT</codeph> stores a comment about a database object. To modify a comment,
issue a new <codeph>COMMENT</codeph> command for the same object. Only one comment string is
stored for each object. To remove a comment, write <codeph>NULL</codeph> in place of the
text string. Comments are automatically dropped when the object is dropped.</p>
<p>Comments can be easily retrieved with the psql meta-commands <codeph>\dd</codeph>,
<codeph>\d+</codeph>, and <codeph>\l+</codeph>. Other user interfaces to retrieve comments
can be built atop the same built-in functions that psql uses, namely
<codeph>obj_description</codeph>, <codeph>col_description</codeph>, and
<codeph>shobj_description</codeph>.</p>
</section>
<section id="section4">
<title>Parameters</title>
<parml>
<plentry>
<pt><varname>object_name</varname></pt>
<pt><varname>table_name.column_name</varname></pt>
<pt><varname>agg_name</varname></pt>
<pt><varname>constraint_name</varname></pt>
<pt><varname>func_name</varname></pt>
<pt><varname>op</varname></pt>
<pt><varname>rule_name</varname></pt>
<pt><varname>trigger_name</varname></pt>
<pd>The name of the object to be commented. Names of tables, aggregates, domains, foreign
tables, functions, indexes, operators, operator classes, sequences, types, and views may
be schema-qualified.
<note>Greenplum Database does not support triggers.</note></pd>
</plentry>
<plentry>
<pt><varname>agg_type</varname></pt>
<pd>An input data type on which the aggregate function operates. To reference a
zero-argument aggregate function, write <codeph>*</codeph> in place of the list of input
data types. </pd>
</plentry>
<plentry>
<pt><varname>sourcetype</varname></pt>
<pd>The name of the source data type of the cast. </pd>
</plentry>
<plentry>
<pt><varname>targettype</varname></pt>
<pd>The name of the target data type of the cast. </pd>
</plentry>
<plentry>
<pt><varname>argmode</varname></pt>
<pd>The mode of a function argument: either <codeph>IN</codeph>, <codeph>OUT</codeph>,
<codeph>INOUT</codeph>, or <codeph>VARIADIC</codeph>. If omitted, the default is
<codeph>IN</codeph>. Note that <codeph>COMMENT ON FUNCTION</codeph> does not actually
pay any attention to <codeph>OUT</codeph> arguments, since only the input arguments are
needed to determine the function's identity. So it is sufficient to list the
<codeph>IN</codeph>, <codeph>INOUT</codeph>, and <codeph>VARIADIC</codeph> arguments.
</pd>
</plentry>
<plentry>
<pt><varname>argname</varname></pt>
<pd>The name of a function argument. Note that <codeph>COMMENT ON FUNCTION</codeph> does
not actually pay any attention to argument names, since only the argument data types are
needed to determine the function's identity. </pd>
</plentry>
<plentry>
<pt><varname>argtype</varname></pt>
<pd>The data type(s) of the function's arguments (optionally schema-qualified), if any.
</pd>
</plentry>
<plentry>
<pt><varname>large_object_oid</varname></pt>
<pd>The OID of the large object. </pd>
</plentry>
<plentry>
<pt>PROCEDURAL</pt>
<pd>This is a noise word. </pd>
</plentry>
<plentry>
<pt><varname>text</varname></pt>
<pd>The new comment, written as a string literal; or <codeph>NULL</codeph> to drop the
comment.</pd>
</plentry>
</parml>
</section>
<section id="section5">
<title>Notes</title>
<p>There is presently no security mechanism for comments: any user connected to a database can
see all the comments for objects in that database (although only superusers can change
comments for objects that they do not own). For shared objects such as databases, roles, and
tablespaces comments are stored globally and any user connected to any database can see all
the comments for shared objects. Therefore, do not put security-critical information in
comments.</p>
</section>
<section id="section6">
<title>Examples</title>
<p>Attach a comment to the table <codeph>mytable</codeph>: </p>
<codeblock>COMMENT ON TABLE mytable IS 'This is my table.';</codeblock>
<p>Remove it again: </p>
<codeblock>COMMENT ON TABLE mytable IS NULL;</codeblock>
</section>
<section id="section7">
<title>Compatibility</title>
<p>There is no <codeph>COMMENT</codeph> statement in the SQL standard.</p>
</section>
</body>
</topic>
gpdb-doc/dita/ref_guide/sql_commands/CREATE_TABLESPACE.xml
浏览文件 @ ce2dab7f
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE topic
PUBLIC "-//OASIS//DTD DITA Composite//EN" "ditabase.dtd">
<topic id="topic1"><title id="cf20941">CREATE TABLESPACE</title><body><p id="sql_command_desc">Defines a new tablespace.</p><section id="section2"><title>Synopsis</title><codeblock id="sql_command_synopsis">CREATE TABLESPACE <varname>tablespace_name</varname> [OWNER <varname>username</varname>]
       FILESPACE <varname>filespace_name</varname></codeblock></section><section id="section3"><title>Description</title><p><codeph>CREATE TABLESPACE</codeph> registers a new tablespace for your
Greenplum Database system. The tablespace name must be distinct from
the name of any existing tablespace in the system. </p><p>A tablespace allows superusers to define an alternative location on
the file system where the data files containing database objects (such
as tables and indexes) may reside.</p><p>A user with appropriate privileges can pass a tablespace name to <codeph><xref
<topic id="topic1">
<title id="cf20941">CREATE TABLESPACE</title>
<body>
<p id="sql_command_desc">Defines a new tablespace.</p>
<section id="section2">
<title>Synopsis</title>
<codeblock id="sql_command_synopsis">CREATE TABLESPACE <varname>tablespace_name</varname> [OWNER <varname>username</varname>] LOCATION '<varname>/path/to/dir</varname>'
[WITH (content<varname>ID_1</varname>='<varname>/path/to/dir1</varname>'[, content<varname>ID_2</varname>='<varname>/path/to/dir2</varname>' ... ])]</codeblock>
</section>
<section id="section3">
<title>Description</title>
<p><codeph>CREATE TABLESPACE</codeph> registers and configures a new tablespace for your
Greenplum Database system. The tablespace name must be distinct from the name of any
existing tablespace in the system. A tablespace is a Greemplum Database system object (a
global object), you can use a tablespace from any database if you have appropriate
privileges.</p>
<p>A tablespace allows superusers to define an alternative host file system location where the
data files containing database objects (such as tables and indexes) reside.</p>
<p>A user with appropriate privileges can pass a tablespace name to <codeph><xref
href="CREATE_DATABASE.xml#topic1" type="topic" format="dita"/></codeph>, <codeph><xref
href="CREATE_TABLE.xml#topic1" type="topic" format="dita"/></codeph>, or <codeph><xref
href="CREATE_INDEX.xml#topic1" type="topic" format="dita"/></codeph> to have the data
files for these objects stored within the specified tablespace.</p><p>In Greenplum Database, there must be a file system location defined for the master, each primary
segment, and each mirror segment in order for the tablespace to have a location to store its
objects across an entire Greenplum system. This collection of file system locations is
defined in a filespace object. A filespace must be defined before you can create a
tablespace. See <codeph>gpfilespace</codeph> in the <i>Greenplum Database Utility Guide</i>
for more information.</p></section><section id="section4"><title>Parameters</title><parml><plentry><pt><varname>tablespacename</varname></pt><pd>The name of a tablespace to be created. The name cannot begin with <codeph>pg_</codeph> or
<codeph>gp_</codeph>, as such names are reserved for system tablespaces. </pd></plentry><plentry><pt>OWNER <varname>username</varname></pt><pd>The name of the user who will own the tablespace. If omitted, defaults
to the user executing the command. Only superusers may create tablespaces,
but they can assign ownership of tablespaces to non-superusers. </pd></plentry><plentry><pt>FILESPACE</pt><pd>The name of a Greenplum Database filespace that was defined using
the <codeph>gpfilespace</codeph> management utility.</pd></plentry></parml></section><section id="section5"><title>Notes</title><p>You must first create a filespace to be used by the tablespace. See <codeph>gpfilespace</codeph>
in the <i>Greenplum Database Utility Guide</i> for more information.</p><p>Tablespaces are only supported on systems that support symbolic links.
</p><p><codeph>CREATE TABLESPACE</codeph> cannot be executed inside a transaction
block.</p></section><section id="section6"><title>Examples</title><p>Create a new tablespace by specifying the corresponding filespace to
use: </p><codeblock>CREATE TABLESPACE mytblspace FILESPACE myfilespace;</codeblock></section><section id="section7"><title>Compatibility</title><p><codeph>CREATE TABLESPACE</codeph> is a Greenplum Database extension.
</p></section><section id="section8"><title>See Also</title><p><codeph><xref href="CREATE_DATABASE.xml#topic1" type="topic" format="dita"/></codeph>,
files for these objects stored within the specified tablespace.</p>
<p>In Greenplum Database, the file system location must exist on all hosts including the hosts
running the master, standby mirror, each primary segment, and each mirror segment. </p>
</section>
<section id="section4">
<title>Parameters</title>
<parml>
<plentry>
<pt><varname>tablespacename</varname></pt>
<pd>The name of a tablespace to be created. The name cannot begin with
<codeph>pg_</codeph> or <codeph>gp_</codeph>, as such names are reserved for system
tablespaces. </pd>
</plentry>
<plentry>
<pt>OWNER <varname>username</varname></pt>
<pd>The name of the user who will own the tablespace. If omitted, defaults to the user
executing the command. Only superusers can create tablespaces, but they can assign
ownership of tablespaces to non-superusers. </pd>
</plentry>
<plentry>
<pt>LOCATION '<varname>/path/to/dir</varname>'</pt>
<pd>The absolute path to the directory (host system file location) that will be the root
directory for the tablespace. When registering a tablepace, the directory should be
empty and must be owned by the Greenplum Database system user. The directory must be
specified by an absolute path name.</pd>
<pd>For each segment instance, you can specify a different directory for the tablespace in
the <codeph>WITH</codeph> clause.</pd>
</plentry>
<plentry>
<pt>content<varname>ID_i</varname>='<varname>/path/to/dir_i</varname>'</pt>
<pd>The value <varname>ID_i</varname> is the content ID for the segment instance.
<varname>/path/to/dir_i</varname> is the absolute path to the host system file location
that the segment instance uses as the root directory for the tablespace. You cannot
specify the content ID of the master instance (<codeph>-1</codeph>). You can specify the
same directory for multiple segments. </pd>
<pd>If a segment instance is not listed in the <codeph>WITH</codeph> clause, Greenplum
Database uses the directory specified in the <codeph>LOCATION</codeph> clause.</pd>
<pd>When registering a tablepace, the directories should be empty and must be owned by the
Greenplum Database system user.</pd>
</plentry>
</parml>
</section>
<section id="section5">
<title>Notes</title>
<p>Tablespaces are only supported on systems that support symbolic links. </p>
<p><codeph>CREATE TABLESPACE</codeph> cannot be executed inside a transaction block.</p>
<p>When creating tablespaces, ensure that file system locations have sufficient I/O speed and
available disk space.</p>
<p>
<codeph>CREATE TABLESPACE</codeph> creates symbolic links from the
<codeph>pg_tblspc</codeph> directory in the master and segment instance data directory to
the directories specified in the command. </p>
<p>The system catalog table <codeph>pg_tablespace</codeph> stores tablespace information. This
command displays the tablespace OID values, names, and
owner.<codeblock>SELECT oid, spcname, spcowner FROM pg_tablespace ;</codeblock></p>
<p>The Greenplum Database built-in function
<codeph>gp_tablespace_location(<varname>tablespace_oid</varname>)</codeph> displays the
tablespace host system file locations for all segment instances. This command lists the
segment database IDs and host system file locations for the tablespace with OID
<codeph>16385</codeph>.<codeblock>SELECT * FROM gp_tablespace_location(16385) </codeblock></p>
</section>
<section id="section6">
<title>Examples</title>
<p>Create a new tablespace and specify the file system location for the master and all segment
instances: </p>
<codeblock>CREATE TABLESPACE mytblspace LOCATION '/gpdbtspc/mytestspace' ;</codeblock>
<p>Create a new tablespace and specify a location for segment instances with content ID 0 and
1. For the master and segment instances not listed in the <codeph>WITH</codeph> clause, the
file system location for the tablespace is specified in the <codeph>LOCATION</codeph>
clause. </p>
<codeblock>CREATE TABLESPACE mytblspace LOCATION '/gpdbtspc/mytestspace' WITH (content0='/temp/mytest', content1='/temp/mytest');</codeblock>
<p>The example specifies the same location for the two segment instances. You can a specify
different location for each segment.</p>
</section>
<section id="section7">
<title>Compatibility</title>
<p><codeph>CREATE TABLESPACE</codeph> is a Greenplum Database extension. </p>
</section>
<section id="section8">
<title>See Also</title>
<p><codeph><xref href="CREATE_DATABASE.xml#topic1" type="topic" format="dita"/></codeph>,
<codeph><xref href="CREATE_TABLE.xml#topic1" type="topic" format="dita"/></codeph>,
<codeph><xref href="CREATE_INDEX.xml#topic1" type="topic" format="dita"/></codeph>,
<codeph><xref href="./DROP_TABLESPACE.xml#topic1" type="topic" format="dita"/></codeph>,
<codeph><xref href="ALTER_TABLESPACE.xml#topic1" type="topic" format="dita"/></codeph>,
<codeph>gpfilespace</codeph> in the <i>Greenplum Database Utility Guide</i>
</p></section></body></topic>
<codeph><xref href="ALTER_TABLESPACE.xml#topic1" type="topic" format="dita"
/></codeph></p>
</section>
</body>
</topic>
Markdown is supported
0% 或 .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑！
想要评论请 注册 或