mirror of
https://git.postgresql.org/git/postgresql.git
synced 2026-02-11 02:37:40 +08:00
For reasons of sheer brain fade, we (I) was calling systable_endscan() immediately after systable_getnext() and expecting the tuple returned by systable_getnext() to still be valid. That's clearly wrong. Move the systable_endscan() down below the tuple usage. Discovered initially by Pavel Stehule and then also by Alvaro. Add a regression test based on Alvaro's testing.
2 lines
45 B
SQL
2 lines
45 B
SQL
grant usage on schema @extschema@ to public;
|