I created a clean 14.3 server with everything default on server creation.
Ran the setup script did the test and again I was able to query the data
successfully. I then decided to create a clean 15.3 server with everything
default. Ran the setup script did the test and was not able to query the
da
On Wed, 2023-09-20 at 14:24 -0700, David G. Johnston wrote:
> On Wed, Sep 20, 2023 at 2:20 PM Erik Wienhold 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 wit
On 2023-09-20 17:53 -0400, Michael Corey wrote:
> To make matters even more strange. I checked the permissions of
> rds_superuser in 15 and 14
>
> For 14
> GRANT pg_monitor, pg_signal_backend, rds_password, rds_replication TO
> rds_superuser WITH ADMIN OPTION;
>
> For 15
> GRANT pg_checkpoint, p
On 2023-09-20 15:19 -0400, Michael Corey wrote:
> Just to be clear in your last response are you saying on your 14.3 you are
> getting the
> ERROR: permission denied for table ref_media_code ?
Yes:
db14=> select version();
On 2023-09-20 14:24 -0700, David G. Johnston wrote:
> On Wed, Sep 20, 2023 at 2:20 PM Erik Wienhold 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 add
On Wed, Sep 20, 2023 at 2:48 PM Michael Corey
wrote:
> How can I check the default privileges?
>
\ddp
https://www.postgresql.org/docs/current/catalog-pg-default-acl.html
David J.
Erik,
To make matters even more strange. I checked the permissions of
rds_superuser in 15 and 14
For 14
GRANT pg_monitor, pg_signal_backend, rds_password, rds_replication TO
rds_superuser WITH ADMIN OPTION;
For 15
GRANT pg_checkpoint, pg_monitor, *pg_read_all_data*, pg_signal_backend,
*pg_write
David,
How can I check the default privileges?
On Wed, Sep 20, 2023 at 5:24 PM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Wed, Sep 20, 2023 at 2:20 PM Erik Wienhold wrote:
>
>> Has your 14.3 some left-over state from previous test runs? I assume
>> the server is not re-created
On Wed, Sep 20, 2023 at 2:20 PM Erik Wienhold 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 CR
Michael Corey ezt írta (időpont: 2023.
szept. 20., Sze, 20:48):
> ... All of the DDL is just the setup for the test case. I ran those steps
> in both databases to setup the exact same environment. The COMMIT is not
> needed for the test out of habit I put it in my setup. The main issue is
> in
Erik,
Just to be clear in your last response are you saying on your 14.3 you are
getting the
ERROR: permission denied for table ref_media_code ?
If this is true then it seems to be something in our setup. This database
may have been upgraded from 13.x to 14. The sten_schema has INHERIT when I
On 2023-09-20 13:17 -0400, Michael Corey wrote:
> PG 14 Server
> psql (14.2, server 14.3)
> You are now connected to database "db14" as user "postgres".
> db14=> \dn+ ref_schema|sten_schema
> List of schemas
> Name |Owner|Access privileges
PG 14 Server
psql (14.2, server 14.3)
You are now connected to database "db14" as user "postgres".
db14=> \dn+ ref_schema|sten_schema
List of schemas
Name |Owner|Access privileges| Description
-+-+---
On 2023-09-20 09:15 -0400, Michael Corey wrote:
> Thanks for responding. All of the DDL is just the setup for the test
> case. I ran those steps in both databases to setup the exact same
> environment.
And both databases start empty or at least in the exact same state?
> The COMMIT is not neede
Erik,
Thanks for responding. All of the DDL is just the setup for the test
case. I ran those steps in both databases to setup the exact same
environment. The COMMIT is not needed for the test out of habit I put it
in my setup. The main issue is in 14.3 I can run this select as user
sten_schema
On 2023-09-19 15:09 -0400, Michael Corey wrote:
> We are experiencing different functionality once we upgraded from Postgres
> 14.3 to Postgres 15.3.
>
> Below is a test case that we created which shows a schema user who has a
> VIEW that accesses a table in another schema. In 14.3 the schema use
We are experiencing different functionality once we upgraded from Postgres
14.3 to Postgres 15.3.
Below is a test case that we created which shows a schema user who has a
VIEW that accesses a table in another schema. In 14.3 the schema user is
able to create the VIEW against the other schema's ta
17 matches
Mail list logo
