MIME-Version: 1.0
References: 
 <CACSdjfMWcR7aJUDf6XNt_yaDi+riz3Ku4EQ-x3xA=Xx1209n2g@mail.gmail.com>
In-Reply-To: 
 <CACSdjfMWcR7aJUDf6XNt_yaDi+riz3Ku4EQ-x3xA=Xx1209n2g@mail.gmail.com>
From: Amit Khandekar <amitdkhan.pg@gmail.com>
Date: Tue, 10 Mar 2026 19:37:10 +0530
Message-ID: 
 <CAJ3gD9eJE_c=eSbBjqAAg+-x2XOSgZ5uYqyAiy4TrJJwxEXyng@mail.gmail.com>
Subject: Re: Inconsistency in owner assignment between INDEX and STATISTICS
To: Shin Berg <sjh910805@gmail.com>
Cc: pgsql-hackers@lists.postgresql.org
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: 
 <https://www.postgresql.org/message-id/CAJ3gD9eJE_c%3DeSbBjqAAg%2B-x2XOSgZ5uYqyAiy4TrJJwxEXyng%40mail.gmail.com>
Precedence: bulk

On Sat, 14 Feb 2026 at 14:18, Shin Berg <sjh910805@gmail.com> wrote:
>
> Hi,
>
> I'd like to raise a small consistency issue between how INDEX and extende=
d STATISTICS handle object ownership, and ask whether aligning them would b=
e desirable.
>
> Current behavior (tested on REL_17_STABLE):
>
> - When a superuser creates an INDEX on another user's table, the index is=
 owned by the *table owner* (see catalog/index.c: index relation's relowner=
 is set from the heap relation's relowner).
> - When a superuser creates STATISTICS on another user's table, the statis=
tics object is owned by the *current user* (statscmds.c: stxowner =3D GetUs=
erId()).

I will try to divide the problem into two questions:

1. Should the statistics object's owner be permanently associated with
the table owner?