OREIGN KEY (par_file_id) REFERENCES
par_log_file(par_file_id);
Version Postgres 13.13
Any help would be appreciated/
--
Michael Corey
in
sync?
On Fri, Feb 16, 2024 at 11:35 AM David G. Johnston <
david.g.johns...@gmail.com> wrote:
> On Fri, Feb 16, 2024 at 9:24 AM Michael Corey <
> michael.corey...@nielsen.com> wrote:
>
>> If I run these two statements I get an error
>> ERROR: relation "part_t
mbinations of this ALTER TABLE statement and none seem
to work. What is the proper way to reattach the identity and the sequence
bearing in mind that I will load the new table with the data from the old
table?
--
Michael Corey
or was it something
changed in the underlying Postgres build.
On Wed, Sep 20, 2023 at 7:11 PM Erik Wienhold wrote:
> 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
> >
> >
,
*pg_write_all_data*, rds_password, rds_replication TO rds_superuser WITH
ADMIN OPTION;
AWS added these permissions, but based on what they do you would think this
would allow the SELECTs in 15.
On Wed, Sep 20, 2023 at 4:40 PM Erik Wienhold wrote:
> On 2023-09-20 15:19 -0400, Michael Corey wr
_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.
>
> David J.
>
>
--
Michael Corey
the original 14 server and made two copies. I kept one as 14 and upgraded
the other to 15. Lastly, I created the test case.
On Wed, Sep 20, 2023 at 3:07 PM Erik Wienhold wrote:
> On 2023-09-20 13:17 -0400, Michael Corey wrote:
> > PG 14 Server
> > psql (14.2, server 14.3)
> >
bases and received different results.
On Wed, Sep 20, 2023 at 12:33 PM Erik Wienhold wrote:
> 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 exac
sten_schema, but in 15.3 I am unable due to a permission issue.
On Tue, Sep 19, 2023 at 8:17 PM Erik Wienhold wrote:
> 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.
> >
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
10 matches
Mail list logo
