On Mon, 2023-03-06 at 13:00 -0800, Joseph Hammerman wrote:
> I am working on splitting up tables that are currently in a single schema into multiple,
> context specific schemas. I would like to do this with minimal downtime from the client
> perspective. I will have prepopulated the existing application client search_path with
> the new schema name.
>
> When inquiring about this in postgresql IRC a concern was raised about data safety,
> due to locks concurrently executing transactions might have on the relation in question
> when the ALTER TABLE ... SET SCHEMA TO ... command is executed (even if done in a transaction).
>
> Would it be data safe if I took an ACCESS EXCLUSIVE lock on the table?
>
> My testing shows that a session with both the old schema and the new schema in its
> path will cleanly determine the new location of the relation - does anyone have any
> caveats or know of any sharp edges I should be aware of here?
I don't think there is any concern with the integrity or consistency of your data;
the transaction system will take care of that. The potential problem is that the
ALTER TABLE will be blocked by concurrent transactions that use the table, and it
will block such concurrent transactions in turn.
So make sure that there are no long running transactions that use the table, then
you should be fine, as long as you COMMIT your transactions right after the ALTER TABLE.
Yours,
Laurenz Albe
