"=?UTF-8?B?6LW15a6H6bmPKOWuh+W9rSk=?=" writes:
> We encountered a scenario where orphaned temporary views are preventing DDL
> operations on a table, such as "ALTER TABLE xxx ALTER COLUMN xxx TYPE xxx."
> The
> corresponding error message is "ERROR: cannot alter type of a column used by
> a view
Hello,
Thank you for your response.
We encountered a scenario where orphaned temporary views are preventing DDL
operations on a table, such as "ALTER TABLE xxx ALTER COLUMN xxx TYPE xxx." The
corresponding error message is "ERROR: cannot alter type of a column used by a
view or rule."
In this case
"=?UTF-8?B?6LW15a6H6bmPKOWuh+W9rSk=?=" writes:
> I have discovered a peculiar issue: after creating a temporary view, if the
> backend process exits abnormally, the temporary view is not cleaned up.
> However,
> if a temporary table is created and the backend process exits abnormally, the
> tempo
