Re: Query regarding function cleanup in extension upgrade path - Mailing list pgsql-general

From Tom Lane
Subject Re: Query regarding function cleanup in extension upgrade path
Date
Msg-id 3113020.1707944175@sss.pgh.pa.us
Whole thread Raw
In response to Re: Query regarding function cleanup in extension upgrade path  (Ayush Vatsa <ayushvatsa1810@gmail.com>)
Responses Re: Query regarding function cleanup in extension upgrade path  (Daniel Gustafsson <daniel@yesql.se>)
List pgsql-general
Ayush Vatsa <ayushvatsa1810@gmail.com> writes:
> Just two follow up queries regarding this -
> 1. Suppose I created a new version 1.1 in which I reduce the C function to
> throw an error then ship it, will users get the .c latest file immediately
> and their old function will throw error but they have to use ALTER
> EXTENSION xyz UPGRADE TO 1.1 to use the latest objects defined in 1.1.sql.
> Is this the correct understanding?

Yes, if you do it like that then once they install the new shlib their
function will be broken until they do ALTER EXTENSION UPGRADE.

> 2. While going through the contrib folder I find that in the regress test
> there are two .out files with respect to a single .sql file, example
> citext.out and citext_1.out wrt citext.sql. Why is it so? Even in git blame
> , I couldn't find much!

We use that when the expected test output is environment-dependent.
If the diff between the .out files isn't pretty self-explanatory,
you can try checking the git log for the "_1.out" file to see why it
was created.

            regards, tom lane



pgsql-general by date:

Previous
From: Greg Sabino Mullane
Date:
Subject: Re: PITR
Next
From: Hannes Erven
Date:
Subject: RowLock and multiple transactions