Re: Changed functionality from 14.3 to 15.3

From: Erik Wienhold <ewie(at)ewie(dot)name>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: Michael Corey <michael(dot)corey(dot)ap(at)nielsen(dot)com>, pgsql-general(at)lists(dot)postgresql(dot)org
Subject: Re: Changed functionality from 14.3 to 15.3
Date: 2023-09-20 22:09:58
Message-ID: h3vbaxp567zs7xwxnytahzhl3mr4eyq5n2oxtc7fko5wjy6hr2@7gbuaahv5w7m
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 2023-09-20 14:24 -0700, David G. Johnston wrote:
> On Wed, Sep 20, 2023 at 2:20 PM Erik Wienhold <ewie(at)ewie(dot)name> wrote:
>
> > Has your 14.3 some left-over state from previous test runs? I assume
> > the server is not re-created for each test run. I was wondering if the
> > roles may still exist and with additional memberships. But then again
> > the script just uses CREATE ROLE. So the roles definitely do not exist
> > beforehand. But what are the actual memberships of sten_schema?
> > Because it must inherit SELECT on ref_media_code on 14.3. It can't be
> > from object_creator because that role also gets newly created.
> >
>
> Your description also suggests that maybe the v14 instance has altered
> default privileges setup that maybe the v15 doesn't have.

Not possible for the roles created in the setup script because the
grantee must exist when defining default privileges. Also \dp shows
only those privileges granted in the setup script.

More questions that need answers:

* How are the databases created?
* Does the template database contribute anything, e.g. event triggers?
* Any other setup scripts involved?

--
Erik

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Erik Wienhold 2023-09-20 23:11:44 Re: Changed functionality from 14.3 to 15.3
Previous Message David G. Johnston 2023-09-20 22:00:04 Re: Changed functionality from 14.3 to 15.3