On 3/3/15 8:04 PM, Kyotaro HORIGUCHI wrote:
>> >Note: The OID alias types don't sctrictly comply the transaction
>> > isolation rules so do not use them where exact transaction
>> > isolation on the values of these types has a
>> > significance. Likewise, since they look as simple constants to
>> > planner so you might get slower plans than the queries joining
>> > the system tables correnspond to the OID types.
Might I suggest:
Note: The OID alias types do not completely follow transaction isolation
rules. The planner also treats them as simple constants, which may
result in sub-optimal planning.
--
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com