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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
