BUG #4618: nolock changes first column name of query result set to 'nolock'

The following bug has been logged online:

Bug reference: 4618
Logged by: brian
Email address: b4kramer(at)yahoo(dot)com
PostgreSQL version: 8.3.5 build1400
Operating system: windows xp
Description: nolock changes first column name of query result set to
'nolock'
Details:

query1 works fine, first column in table is called movieid1:
select * from netflix.ratings where movieid = 1

query2 is a bug and should work just fine, but gives error:
ERROR: column "movieid" does not exist
LINE 2: select * from netflix.ratings with (nolock) where movieid = ...
^

********** Error **********

ERROR: column "movieid" does not exist
SQL state: 42703
Character: 52'
select * from netflix.ratings with (nolock) where movieid = 1

query3 is the similar bug, this query works but should not since field name
is 'movieid' not 'nolock', result set displays 'nolock' instead of 'movieid'
as well:
select * from netflix.ratings with (nolock) where nolock = 1

query4 changes first column name to 'nolock' and leaves all other column
names as normal:
select * from netflix.ratings with (nolock) limit 1