Re: fix schema ownership on first connection preliminary - Mailing list pgsql-patches

From Christopher Kings-Lynne
Subject Re: fix schema ownership on first connection preliminary
Date
Msg-id 410D9FD8.8040208@familyhealth.com.au
Whole thread Raw
In response to Re: fix schema ownership on first connection preliminary patch v2  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-patches
> I'm also wondering about what side-effects this will have on pg_dump
> behavior.  In particular, will pg_dump try to "ALTER OWNER public",
> and if so will that be appropriate?  We haven't previously needed to
> assume that we are restoring into a database with the same datowner as
> we dumped from...

In my batch of pg_dump patches that have gone in, pg_dump will now do
exactly that.  The reason was so that if someone altered the owner of
their public schema, it should be dumped like that.

Chris

pgsql-patches by date:

Previous
From: Tom Lane
Date:
Subject: Re: fix for parameterized queries in DECLARE CURSOR statements
Next
From: Christopher Kings-Lynne
Date:
Subject: Re: Fix for OWNER TO breaking ACLs