From: voidlinux-github@inbox.vuxu.org
To: ml@inbox.vuxu.org
Subject: Re: [PR PATCH] [Closed]: postgresql: update to 12.1
Date: Wed, 08 Jan 2020 20:27:15 +0100 [thread overview]
Message-ID: <20200108192715.CyZWNKmCsu4C3GvhVWnj58zLNtynP_kzPTOQ43uGPVc@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-18103@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
There's a closed pull request on the void-packages repository
postgresql: update to 12.1
https://github.com/void-linux/void-packages/pull/18103
Description:
[`createlang`](https://stackoverflow.com/questions/52107949/createlang-command-not-found-in-postgres#answer-52109145) and [`droplang`](https://www.postgresql.org/docs/9.6/app-droplang.html) has been deprecated since PostgreSQL 9.1
`plctcl` - Since `createlang` has been deprecated, `CREATE EXTENSION {pltcl,pltclu}` is needed to use it (I don't use this, so could someone please check if it's correct). See [here](https://www.postgresql.org/docs/10/pltcl-overview.html)
New versioning policy since [PostgreSQL 10](https://www.postgresql.org/support/versioning/)
[PostgreSQL 12 release notes](https://www.postgresql.org/docs/current/release-12.html)
[PostgreSQL 11 release notes](https://www.postgresql.org/docs/current/release-11.html)
[PostgreSQL 10 release notes](https://www.postgresql.org/docs/current/release-10.html)
Since more than 1 version has passed, `pg_upgrade` or `pg_dumpall` might be needed to be run on any DBs.
prev parent reply other threads:[~2020-01-08 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 10:08 [PR PATCH] " voidlinux-github
2020-01-08 17:05 ` voidlinux-github
2020-01-08 17:06 ` voidlinux-github
2020-01-08 19:26 ` voidlinux-github
2020-01-08 19:27 ` voidlinux-github [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200108192715.CyZWNKmCsu4C3GvhVWnj58zLNtynP_kzPTOQ43uGPVc@z \
--to=voidlinux-github@inbox.vuxu.org \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).