On 10 August 2017 at 12:14, Tom Lane wrote:
> Ben Leslie writes:
Thanks for the quick response, I appreciate it.
> I'm wondering if I can/should expect schema renames to be isolated.
Nope, you should not.
That's fine. I think I can achieve what I want using an alternative
approach.
> This
On Thu, Aug 10, 2017 at 2:14 PM, Tom Lane wrote:
> Ben Leslie writes:
>> I'm wondering if I can/should expect schema renames to be isolated.
>
> Nope, you should not.
>
> This is not an especially easy thing to fix, because to have the system
> behave as you wish it did, your second transaction w
Ben Leslie writes:
> I'm wondering if I can/should expect schema renames to be isolated.
Nope, you should not.
This is not an especially easy thing to fix, because to have the system
behave as you wish it did, your second transaction would have to be
ignoring already-committed DDL changes, and i
I'm wondering if I can/should expect schema renames to be isolated.
For example, I have two schemas "test" and "test_new". Each with a "test"
table (with same columns, but different data).
In one transaction I'm renaming the schemas test => test_old, test_new =>
test. I.e.:
BEGIN;
ALTER SCHEMA t
