You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Commit 00e8862 changes UPDATE to DELETE and INSERT as a workaround to issue #13500. It doesn't properly translate the UPDATE to DELETE and INSERT because the conditions of the UPDATE don't match the condition of the DELETE. Actually, in the first place, it didn't have enough conditions.
If using the unique index, it should condition on all three columns. Before, it had only two columns, and after, it had only one column. One possibility right now is to have user's public.pg_stat_get_progress_info get deleted.
The text was updated successfully, but these errors were encountered:
jasonyb
changed the title
[YSQL] Fix V31 migration to not affect other pg_stat_get_progress_info
[YSQL] Fix migrations to properly update pg_proc
Feb 2, 2023
Summary:
The condition of the pg_proc `UPDATE`/`DELETE` in migrations V17, V22, V31 is not specific enough - use all 3 columns of `pg_proc_proname_args_nsp_index` in the condition.
Test Plan: Jenkins: test regex: .*TestYsqlUpgrade.*
Reviewers: jason
Reviewed By: jason
Differential Revision: https://phabricator.dev.yugabyte.com/D22719
Jira Link: DB-5369
Description
Commit 00e8862 changes UPDATE to DELETE and INSERT as a workaround to issue #13500. It doesn't properly translate the UPDATE to DELETE and INSERT because the conditions of the UPDATE don't match the condition of the DELETE. Actually, in the first place, it didn't have enough conditions.
\d pg_proc
showsIf using the unique index, it should condition on all three columns. Before, it had only two columns, and after, it had only one column. One possibility right now is to have user's public.pg_stat_get_progress_info get deleted.
The text was updated successfully, but these errors were encountered: