mirror of https://github.com/postgres/postgres
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.pull/12/head
parent
d2de44c2ce
commit
99f2f3c19a
@ -0,0 +1 @@ |
||||
grant usage on schema @extschema@ to public; |
||||
@ -0,0 +1,5 @@ |
||||
comment = 'test_ext6' |
||||
default_version = '1.0' |
||||
relocatable = false |
||||
superuser = true |
||||
schema = 'test_ext6' |
||||
Loading…
Reference in new issue