Go to file
Sandro Santilli d1990f1765 Provide upgrade paths
Mainly from 0.1.0 and 0.1.1
Includes 0.2.0dev to next and back
2014-05-28 09:48:32 +02:00
expected Fix recursive DDL trigger on create table 2014-05-28 09:02:02 +02:00
scripts-available Fix recursive DDL trigger on create table 2014-05-28 09:02:02 +02:00
scripts-enabled Remove CDB_SearchPath.sql from the set of scripts loaded directly 2014-05-19 13:26:01 +02:00
sql Fix recursive DDL trigger on create table 2014-05-28 09:02:02 +02:00
test Fix cartodbfication of already-cartodbfied tables in presence of views 2014-05-23 16:54:36 +02:00
util Add tool to create upgrades 2014-05-23 18:16:10 +02:00
.gitignore Add cdb_version() function 2014-05-08 10:07:47 +02:00
.travis.yml [Travis] Drop env grepping (interrupts the build on no-match) 2014-05-08 12:58:05 +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 Fix extension requires directive 2014-05-16 11:39:15 +02:00
LICENSE Update LICENSE, set copyright ownership to Vizzuality 2014-05-06 07:33:01 +02:00
Makefile Provide upgrade paths 2014-05-28 09:48:32 +02:00
NEWS Move DDL triggers and extension postamble under scripts-available 2014-05-23 17:40:14 +02:00
README.md Update instructions to install in existing cartodb databases 2014-05-08 19:01:32 +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 !

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;