Re: Identifying user-created objects

From: Amit Langote <amitlangote09(at)gmail(dot)com>
To: Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Identifying user-created objects
Date: 2020-02-10 03:54:10
Message-ID: CA+HiwqGsW3cgVRQ6CyRpAx9y+vCYxA=YVcPS6RfR9XCyA_1smQ@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sawada-san,

On Mon, Feb 10, 2020 at 12:25 PM Masahiko Sawada
<masahiko(dot)sawada(at)2ndquadrant(dot)com> wrote:
> > > > On Thu, Feb 06, 2020 at 04:25:47PM +0900, Amit Langote wrote:
> > > > > About the implementation, how about defining a static inline function,
> > > > > say is_user_object(), next to FirstNormalObjectId's definition and
> > > > > make pg_is_user_object() call it? There are a few placed in the
> > > > > backend code that perform the same computation as pg_is_user_object(),
> > > > > which could be changed to use is_user_object() instead.
>
> Attached the updated version patch that includes regression tests. And
> I have registered this to the next commit fest.

Thank you.

Any thoughts on the above suggestion?

Regards,
Amit

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2020-02-10 03:55:09 Re: Postgres 32 bits client compilation fail. Win32 bits client is supported?
Previous Message Pengzhou Tang 2020-02-10 03:37:19 Re: Parallel grouping sets