Re: Install extensions using update scripts (was Re: Remove superuser() checks from pgstattuple)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Stephen Frost <sfrost(at)snowman(dot)net>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Install extensions using update scripts (was Re: Remove superuser() checks from pgstattuple)
Date: 2016-09-09 01:23:45
Message-ID: 20160909012345.r677qmilghxsiwlj@alap3.anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 2016-09-07 13:44:28 -0400, Tom Lane wrote:
> + <sect2>
> + <title>Installing Extensions using Update Scripts</title>
> +
> + <para>
> + An extension that has been around for awhile will probably exist in

Wanted to cry typo for 'awhile' here, but apparently that's actually a
word. The German in me is pleased.

> + several versions, for which the author will need to write update scripts.
> + For example, if you have released a <literal>foo</> extension in
> + versions <literal>1.0</>, <literal>1.1</>, and <literal>1.2</>, there
> + should be update scripts <filename>foo--1.0--1.1.sql</>
> + and <filename>foo--1.1--1.2.sql</>.
> + Before <productname>PostgreSQL</> 10, it was necessary to create new
> + script files <filename>foo--1.1.sql</> and <filename>foo--1.2.sql</>
> + containing the same changes, or else the newer versions could not be

Maybe replace "same changes" "directly creating the extension's
contents" or such?

- Andres

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2016-09-09 01:28:40 Re: Quorum commit for multiple synchronous replication.
Previous Message Andres Freund 2016-09-09 01:19:54 Re: Install extensions using update scripts (was Re: Remove superuser() checks from pgstattuple)