[docs] CTAS on PostgreSQL needs commit to apply (#8367)

* [docs] New, document need for PG to use autocommit for CTAS
This commit is contained in:
Daniel Vaz Gaspar 2019-10-17 14:54:02 +01:00 committed by GitHub
parent c422b492eb
commit c62b2f4340
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 22 additions and 0 deletions

View File

@ -579,6 +579,9 @@ object gets unpacked into the
while the ``metadata_params`` get unpacked into the
`sqlalchemy.MetaData <https://docs.sqlalchemy.org/en/rel_1_2/core/metadata.html#sqlalchemy.schema.MetaData>`_ call. Refer to the SQLAlchemy docs for more information.
.. note:: If your using CTAS on SQLLab and PostgreSQL
take a look at :ref:`ref_ctas_engine_config` for specific ``engine_params``.
Schemas (Postgres & Redshift)
-----------------------------

View File

@ -122,3 +122,22 @@ database configuration:
Here, "version" should be the version of your Presto cluster. Support for this
functionality was introduced in Presto 0.319.
.. _ref_ctas_engine_config:
Create Table As (CTAS)
''''''''''''''''''''''
You can use ``CREATE TABLE AS SELECT ...`` statements on SQLLab. This feature can be toggled on
and off at the database configuration level.
Note that since ``CREATE TABLE..`` belongs to a SQL DDL category. Specifically on PostgreSQL, DDL is transactional,
this means that to properly use this feature you have to set ``autocommit`` to true on your engine parameters:
.. code-block:: json
{
...
"engine_params": {"isolation_level":"AUTOCOMMIT"},
...
}