Re: A slightly misleading comment in GetNewObjectId()

From: Shawn Debnath <sdn(at)amazon(dot)com>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>, Pg Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: A slightly misleading comment in GetNewObjectId()
Date: 2018-08-16 17:53:38
Message-ID: 20180816175338.GA27190@60f81dc409fc.ant.amazon.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, Aug 16, 2018 at 11:36:58AM -0400, Robert Haas wrote:
> On Thu, Aug 16, 2018 at 12:47 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> writes:
> >> That makes it sound like a mere optimisation, but since commit
> >> 8e18d04d4da user-created objects are not allowed to have OIDs below
> >> that threshold. So I propose the attached tweak.
> >
> > +1
>
> Looks good to me, too.

+1 and thanks for pointing to the commit which makes this a reality.

--
Shawn Debnath

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Shay Rojansky 2018-08-16 17:54:25 Re: Stored procedures and out parameters
Previous Message Jeremy Finzel 2018-08-16 17:53:26 Re: Repeatable Read Isolation in SQL running via background worker