Re: Are these metadata ALTER TABLE commands transactionally safe?

On Thu, May 14, 2026 at 5:26 PM David G. Johnston <
david(dot)g(dot)johnston(at)gmail(dot)com> wrote:

> On Thursday, May 14, 2026, Ron Johnson <ronljohnsonjr(at)gmail(dot)com> wrote:
>
>> PG 17.9
>>
>> BEGIN;
>> ALTER TABLE x RENAME TO x_hold;
>> ALTER TABLE y.x SET SCHEMA a;
>> ALTER TABLE x OWNER TO foo;
>> COMMIT;
>>
>>
> Define “transactionally safe”.
>

Any open transactions will still see the original tables.

>
>
>> I don't trust the validity of synthetic tests when Prod is ill-behaved
>> JDBC connections.
>>
>>
> Then do them over a local connection using psql?
>

The applications which I don't want to throw errors are ill-behaved JDBC
connections. Sorry for the ambiguity.

--
Death to <Redacted>, and butter sauce.
Don't boil me, I'm still alive.
<Redacted> lobster!