You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
Go to file
Andy Eschbacher 3ad3038c5e
fixed symlink path, other minor items
9 years ago
expected Do not grant select permission to public user 10 years ago
scripts-available initial commit 9 years ago
scripts-enabled fixed symlink path, other minor items 9 years ago
sql Do not grant select permission to public user 10 years ago
test fixed symlink path, other minor items 9 years ago
util Do not force re-cartodbfication on CREATE FROM unpackaged 10 years ago
.gitignore Ignore idea ide based settings 10 years ago
.travis.yml Merge branch 'master' into CDB-3497 10 years ago
CONTRIBUTING.md Fixes typos 10 years ago
LICENSE Update LICENSE, set copyright ownership to Vizzuality 11 years ago
Makefile fix indentation of Makefile #73 10 years ago
NEWS.md Fix upgrade of CDB_StringToDate function #73 10 years ago
README.md Adds highlighting 10 years ago
cartodb.control.in List plpythonu requirement first, so get pg_catalog scanned before public 10 years ago
cartodb_version.sql.in Refuse to create new extension if legacy code is present on database 11 years ago

README.md

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".