Postgres 13 by Default
Alex Pearson
Platter CTOWe're proud to announce that Postgres instances are now using 13 by default. This upgrade will apply to all new Postgres instances created with platter postgres create
.
#
Getting StartedTo get started with Platter's branching Postgres databases for the first time, take a look at the Quick Start.
#
About This UpdateThere are no updates required for existing platter
CLI users. All new instances created will use version 13 by default.
#
FeaturesThe upgrade to Postgres 13 brings with it some important new features. Besides those included in Postgres itself, we want to highlight one that affects Platter users the most: trusted extensions.
It's common to extend the base types and functions that ship with a new postgres database through CREATE EXTENSION
. Many popular and often critical features are packages as extensions, including basic cryptography, hstore
data types, and UUID support.
In previous versions of Postgres, only superusers could create an extension. This was often confusing, as even database owners couldn't leverage these extensions without help from an admin. In the case of Platter Postgres, that admin is, of course, Platter, and we do our best to enable extensions for users on a case-by-case basis (email at [email protected]
if you need an extension enabled on a previous version of Postgres).
But with Postgres 13, some of these most common extensions are now "trusted", and owners of a database can CREATE
that extension without needing superuser permission. For new instances on the shared cluster, the following extensions are now trusted and available for use with CREATE EXTENSION
:
btree_gin
btree_gist
citext
cube
dict_int
fuzzystrmatch
hstore
intarray
isn
lo
ltree
pg_trgm
pgcrypto
tablefunc
tsm_system_rows
tsm_system_time
unaccent
uuid-ossp
In addition, plpgsql
is both trusted and installed by default.
#
Support and FeedbackThanks for giving this update a try! If you have any questions or feedback, please let us know in the #kitchen
Slack channel or by emailing us at [email protected]
.