perfSONAR User Q&A and Other Discussion

Hi Mark,

Thanks for the explanation!

Cheers,

Simon

On 12/03/2018, at 21:43, Mark Feit <> wrote:

Simon peter green writes:

 

What caused it in the first place?

 

To follow onto what Valentin said:

 

A few of the stored procedures in the database have had signature changes over time.  When that happens, the old version of the function has to be explicitly deleted or PostgreSQL will throw up its hands when you try to invoke the function in an ambiguous way.  I made a mistake in the development code that did the deletion; that lived for about 24 hours in the nightly build and made its way into staging when a merge didn’t happen correctly.

 

To prevent this from happening in the future, what we ship with 4.1 will include code that scrubs out all versions of a stored procedure before building the current one.  We’re also going to be discussing some unrelated changes to our development process that will have the side effect of making the merge problem less likely to occur.

 

--Mark