mirror of
https://github.com/postgres/postgres.git
synced 2026-04-24 15:47:01 -04: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.
1 line
45 B
SQL
1 line
45 B
SQL
grant usage on schema @extschema@ to public;
|