diff --git a/gpdb-doc/dita/ref_guide/feature_summary.xml b/gpdb-doc/dita/ref_guide/feature_summary.xml index 2226b4c438ceb0a2b6ba106089093bc000c3fcaf..0ce297ca339c3d143644e6f30aeb2beb15f12c28 100644 --- a/gpdb-doc/dita/ref_guide/feature_summary.xml +++ b/gpdb-doc/dita/ref_guide/feature_summary.xml @@ -198,14 +198,16 @@ NEXT 10 ROWS ONLY;

Greenplum Greenplum and PostgreSQL Compatibility -

Greenplum Database is based on PostgreSQL 8.3 with additional features from newer - PostgreSQL releases. To support the distributed nature and typical workload of a 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 .

+

Greenplum Database is based on PostgreSQL 9.4. To support the distributed nature and + typical workload of a 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 .Greenplum Database does not support the PostgreSQL large object facility for streaming user data that is stored in + large-object structures.

SQL Support in Greenplum Database diff --git a/gpdb-doc/dita/ref_guide/sql_commands/COMMENT.xml b/gpdb-doc/dita/ref_guide/sql_commands/COMMENT.xml index 7f4c589a50ca2e68365324c68eda41bb3dfb935d..14227dfbd70f966990df795dd7dd022355c96c53 100644 --- a/gpdb-doc/dita/ref_guide/sql_commands/COMMENT.xml +++ b/gpdb-doc/dita/ref_guide/sql_commands/COMMENT.xml @@ -104,6 +104,12 @@ IS 'text' large_object_oid The OID of the large object. + + Greenplum Database does not support the PostgreSQL large object facility for streaming user data that is stored + in large-object structures. + PROCEDURAL diff --git a/gpdb-doc/dita/ref_guide/system_catalogs/pg_largeobject.xml b/gpdb-doc/dita/ref_guide/system_catalogs/pg_largeobject.xml index 0fa6386613423e7a4f6732f2c74037d70e701155..47a7b0536e5bbf602f9fd7484449ea5f62a65fc5 100644 --- a/gpdb-doc/dita/ref_guide/system_catalogs/pg_largeobject.xml +++ b/gpdb-doc/dita/ref_guide/system_catalogs/pg_largeobject.xml @@ -1,7 +1,11 @@ -pg_largeobject

The pg_largeobject system catalog table holds the data +pg_largeobject + Greenplum Database does not support the PostgreSQL large object facility for streaming user data that is stored + in large-object structures.

The pg_largeobject system catalog table holds the data making up 'large objects'. A large object is identified by an OID assigned when it is created. Each large object is broken into segments or 'pages' small enough to be conveniently stored as rows in pg_largeobject. diff --git a/gpdb-doc/dita/utility_guide/client_utilities/pg_dump.xml b/gpdb-doc/dita/utility_guide/client_utilities/pg_dump.xml index b6243b1d5440fa43c99148ef939f3116ca19753e..70bfdfe97b0001b57481f092bf4c26f31a90ff5c 100644 --- a/gpdb-doc/dita/utility_guide/client_utilities/pg_dump.xml +++ b/gpdb-doc/dita/utility_guide/client_utilities/pg_dump.xml @@ -80,7 +80,12 @@ Include large objects in the dump. This is the default behavior except when --schema, --table, or --schema-only is specified, so the -b switch is - only useful to add large objects to selective dumps. + only useful to add large objects to selective dumps.Greenplum Database does not + support the PostgreSQL large object facility for streaming user data that is + stored in large-object structures. + --binary-upgrade diff --git a/gpdb-doc/dita/utility_guide/client_utilities/pg_restore.xml b/gpdb-doc/dita/utility_guide/client_utilities/pg_restore.xml index 8d52d94ed720ba92d5d8346b1bf1ded9e2528d82..4c8ea01440f41871ba577abe4dcc0c2968824c68 100644 --- a/gpdb-doc/dita/utility_guide/client_utilities/pg_restore.xml +++ b/gpdb-doc/dita/utility_guide/client_utilities/pg_restore.xml @@ -275,11 +275,6 @@ disable triggers on user tables before inserting the data then emits commands to re-enable them after the data has been inserted. If the restore is stopped in the middle, the system catalogs may be left in the wrong state.

-

pg_restore cannot restore large objects selectively, - for instance only those for a single table. If an archive contains large - objects, then all large objects will be restored, or none will be - restored if they are excluded by the -L, - -t, or another option.

See also the pg_dump documentation for details on limitations of pg_dump.

Once restored, it is wise to run ANALYZE on each restored table so the diff --git a/gpdb-doc/dita/utility_guide/client_utilities/psql.xml b/gpdb-doc/dita/utility_guide/client_utilities/psql.xml index b0c5101f2c761e649e32902fcca9266dd05f4f2d..c05431314651143741e998fa3cc6ee874c8b5df9 100644 --- a/gpdb-doc/dita/utility_guide/client_utilities/psql.xml +++ b/gpdb-doc/dita/utility_guide/client_utilities/psql.xml @@ -469,6 +469,12 @@ testdb=# \dl This is an alias for \lo_list, which shows a list of large objects. + + Greenplum Database does not support the PostgreSQL large object facility for streaming user data that is stored + in large-object structures. + \dn [schema_pattern] | \dn+