Affected both thin and jdbc v2 drivers.
jdbc spec says :
but in fact it is a position in the metadata table itself, not position in the original table.
For example we have table
Oridinal number for val3 is 4, but if we specified patterns that leave only 1 result (PUBLIC.Person.val3) returned value will be 1. If we select 2 columns by pattern - 2 or 1 and so on.