Re: 10.4 upgrade, function markings, and template0 - Mailing list pgsql-general

From Dominic Jones
Subject Re: 10.4 upgrade, function markings, and template0
Date
Msg-id 20180514155138.9b6ce56efdb3c20272d560ee@xmission.com
Whole thread Raw
In response to Re: 10.4 upgrade, function markings, and template0  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-general
On Mon, 14 May 2018 17:02:25 -0400
Tom Lane <tgl@sss.pgh.pa.us> wrote:

> Dominic Jones <jonesd@xmission.com> writes:
> > The PostgreSQL 10.4 upgrade involves changes to some function markings (see release notes, E.1.2, second and third
bulletpoints for specifics). One way to make these changes is to use `ALTER FUNCTION` to change the functions in your
existingdatabases. While this was mainly straightforward, I'm unclear on whether the `template0` database must be
changedin this manner or if it is automatically updated when the upgrade is applied. The documentation indicates that
ingeneral you shouldn't manually change the `template0` database.
 
> 
> Yes, you'd need to fix it in template0 as well, or you risk
> subsequently-created databases not having the fix.  See previous
> minor releases where we've given more painstaking detail about
> applying catalog corrections, e.g. 9.6.4:
> 
> https://www.postgresql.org/docs/current/static/release-9-6-4.html
> 
> I didn't bother with spelling it all out in full detail this time,
> which maybe was a mistake, but I felt that probably most users
> wouldn't need to bother with these changes at all (unlike the case
> where a catalog correction is security-related).
> 
>             regards, tom lane
> 

Yes, the link does address the issue and answer the question. It looks like I didn't see the previous upgrade's
discussionbecause the change to which it was tied didn't appear to be relevant to the database deployment involved.
 


-- 
Dominic Jones <jonesd@xmission.com>


pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: 10.4 upgrade, function markings, and template0
Next
From: Dale Seaburg
Date:
Subject: Re: Strange error in Windows 10 Pro