"Andy Kriger" <akriger@greaterthanone.com> writes:
> It doesn't lock the row from being read. I want to make sure the row cannot
> be read until I have done my read and updated if necessary.
Why?
You're really swimming upstream against the notion of MVCC if you want
to prevent pure readers from proceeding while your update transaction
runs. Since you claim to be concerned about bottlenecks, I do not see
why you shouldn't embrace the MVCC worldview, rather than fighting it
tooth and nail.
regards, tom lane