Go to file
2014-07-16 12:30:19 +02:00
expected Fix potential infinite loop in CDB_QueryStatements 2014-06-05 15:00:57 +02:00
scripts-available CDB_SetUserQuotaInBytes returning set value instead of previous value. 2014-07-07 10:36:51 +02:00
scripts-enabled CDB-3094 enables organizations functions 2014-06-17 11:43:38 +02:00
sql Fix potential infinite loop in CDB_QueryStatements 2014-06-05 15:00:57 +02:00
test CDB_SetUserQuotaInBytes returning set value instead of previous value. 2014-07-07 10:36:51 +02:00
util Do not force re-cartodbfication on CREATE FROM unpackaged 2014-06-11 10:24:53 +02:00
.gitignore Add cdb_version() function 2014-05-08 10:07:47 +02:00
.travis.yml Have travis specify "postgres" as the testsuite running user 2014-06-18 11:54:28 +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 List plpythonu requirement first, so get pg_catalog scanned before public 2014-06-11 16:27:11 +02:00
CONTRIBUTING Move in-place upgrade of functions from README to CONTRIBUTING 2014-06-17 10:43:49 +02:00
LICENSE Update LICENSE, set copyright ownership to Vizzuality 2014-05-06 07:33:01 +02:00
Makefile Version 0.3.0 2014-07-16 12:30:19 +02:00
NEWS Update NEWS 2014-07-15 16:57:23 +02:00
README.md Add note about the need to be postgresql superuser when running tests 2014-06-18 11:52:01 +02:00

cartodb-postgresql

[Build Status] (http://travis-ci.org/CartoDB/cartodb-postgresql)

PostgreSQL extension for CartoDB

See https://github.com/CartoDB/cartodb/wiki/CartoDB-PostgreSQL-extension

Dependencies

Install

make all install

Test installation

make installcheck

NOTE: if test_ddl_triggers fails it's likely due to an incomplete installation of schema_triggers: you need to add schema_triggers.so to the shared_preload_libraries setting in postgresql.conf !

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

Enable database

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

CREATE EXTENSION postgis;
CREATE EXTENSION schema_triggers;
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 schema_triggers;
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".