Go to file
2018-09-10 15:42:54 +02:00
doc Add CDB_EstimateRowCount function 2017-04-07 15:35:48 +02:00
expected Remove ddl triggers specs 2016-01-21 11:46:39 +01:00
scripts-available Jenks: Fix multiple bugs 2018-09-10 15:42:35 +02:00
scripts-enabled Add CDB_EstimateRowCount function 2017-04-07 15:35:48 +02:00
sql Remove ddl triggers specs 2016-01-21 11:46:39 +01:00
test Jenks: Add inverse request test 2018-09-10 15:42:54 +02:00
util Do not force re-cartodbfication on CREATE FROM unpackaged 2014-06-11 10:24:53 +02:00
.gitignore Ignore vim temporal files 2015-08-14 13:58:10 +02:00
.travis.yml Travis: Test with Postgresql 9.5 and 10, and Postgis 2.4 2018-09-04 17:25:03 +02:00
carto-package.json PostGIS uses 4 numbers 2018-08-17 10:48:21 +02:00
cartodb_version.sql.in Refuse to create new extension if legacy code is present on database 2014-05-14 12:39:53 +02:00
cartodb.control.in Remove schema_triggers 2015-11-04 17:06:54 +01:00
CONTRIBUTING.md Update CONTRIBUTING with information about function labels 2017-11-13 09:35:20 +01:00
LICENSE Update LICENSE, set copyright ownership to Vizzuality 2014-05-06 07:33:01 +02:00
Makefile Release 0.23.2 2018-07-20 14:15:05 +02:00
NEWS.md _cdb_estimated_extent: Adapt to ST_EstimatedExtent change 2018-09-04 18:21:28 +02:00
README.md updates pg version based on cdb_quantiles update 2018-04-25 09:09:55 -04:00

cartodb-postgresql

Build Status

PostgreSQL extension for CartoDB

See the cartodb-postgresql wiki.

Dependencies

Install

make all install

Test installation

make installcheck

NOTE: you need to run the installcheck as a superuser, use PGUSER env variable if needed, like: PGUSER=postgres make installcheck

NOTE: the tests need to run against a clean postgres instance, if you have some roles already created test will likely fail due publicuser not being dropped.

Enable database

In a database that needs to be turned into a "cartodb" user database, run:

CREATE EXTENSION postgis;
CREATE EXTENSION cartodb;

Migrate existing cartodb database

When upgrading an existing cartodb user database, the cartodb extension can be migrated from the "unpackaged" version. The procedure will copy the data from public.CDB_TableMetada to cartodb.CDB_TableMetadata, re-cartodbfy all tables using old functions in triggers and drop the cartodb functions from the 'public' schema. All new cartodb objects will be in the "cartodb" schema.

CREATE EXTENSION postgis FROM unpackaged;
CREATE EXTENSION cartodb FROM unpackaged;

Update cartodb extension

Updating the version of cartodb extension installed in a database is done using ALTER EXTENSION.

ALTER EXTENSION cartodb UPDATE TO '0.1.1';

The target version needs to be installed on the system first (see Install section).

If the "TO 'x.y.z'" part is omitted, the extension will be updated to the latest installed version, which you can find with the following command:

grep default_version `pg_config --sharedir`/extension/cartodb.control

Updates are performed by PostgreSQL by loading one or more migration scripts as needed to go from the installed version S to the target version T. All migration scripts are in the "extension" directory of PostgreSQL:

ls `pg_config --sharedir`/extension/cartodb*

During development the cartodb extension version doesn't change with every commit, so testing latest change requires special steps documented in the CONTRIBUTING document, under "Testing changes live".

Limitations

  • The main schema of an organization user must have one only owner (the user).