Re: Resource Owner reassign Locks - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: Resource Owner reassign Locks
Date
Msg-id CAMkU=1xdTpjfz5CVgVZ6rZde8eyhgjiqDK2+ENfKRVrwJKRstQ@mail.gmail.com
Whole thread
In response to Re: Resource Owner reassign Locks  (Andres Freund <andres@anarazel.de>)
Responses Re: Resource Owner reassign Locks
List pgsql-hackers
On Fri, Jul 3, 2015 at 12:59 AM, Andres Freund <andres@anarazel.de> wrote:
On 2015-06-07 13:44:08 -0700, Jeff Janes wrote:
> I'd like to advocate for back-patching this to 9.0, 9.1, and 9.2.  It has
> run without problems for a while now, and it can be considered a bug that
> systems with a very large number of objects cannot be upgraded in a
> reasonable time.

In that case, how about working on a version for <= 9.2 (single one
should suffice)? This will likely include a bunch of wrapper functions
to avoid changing the API in the back branches.

Greetings,

Andres Freund

Unfortunately I don't know what that means about the API.  Does it mean that none of the functions declared in any .h file can have their signatures changed?  But new functions can be added?

Thanks,

Jeff

pgsql-hackers by date:

Previous
From: Jeff Janes
Date:
Subject: Re: Freeze avoidance of very large table.
Next
From: Andres Freund
Date:
Subject: Re: Resource Owner reassign Locks