public inbox for [email protected]
help / color / mirror / Atom feedFrom: Amit Khandekar <[email protected]>
To: Shin Berg <[email protected]>
Cc: [email protected]
Subject: Re: Inconsistency in owner assignment between INDEX and STATISTICS
Date: Tue, 10 Mar 2026 19:37:10 +0530
Message-ID: <CAJ3gD9eJE_c=eSbBjqAAg+-x2XOSgZ5uYqyAiy4TrJJwxEXyng@mail.gmail.com> (raw)
In-Reply-To: <CACSdjfMWcR7aJUDf6XNt_yaDi+riz3Ku4EQ-x3xA=Xx1209n2g@mail.gmail.com>
References: <CACSdjfMWcR7aJUDf6XNt_yaDi+riz3Ku4EQ-x3xA=Xx1209n2g@mail.gmail.com>
On Sat, 14 Feb 2026 at 14:18, Shin Berg <[email protected]> wrote:
>
> Hi,
>
> I'd like to raise a small consistency issue between how INDEX and extended STATISTICS handle object ownership, and ask whether aligning them would be 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 statistics object is owned by the *current user* (statscmds.c: stxowner = GetUserId()).
I will try to divide the problem into two questions:
1. Should the statistics object's owner be permanently associated with
the table owner?
view thread (7+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected]
Subject: Re: Inconsistency in owner assignment between INDEX and STATISTICS
In-Reply-To: <CAJ3gD9eJE_c=eSbBjqAAg+-x2XOSgZ5uYqyAiy4TrJJwxEXyng@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox