Nope. I'm feeling a strong urge to go fix it for 8.1 though.
The question from the previous mail still stands: would anybody's
applications be broken if we change the MVCC behavior of large objects?
Could you provide an instance where it might? I had always assumed (I
know, never assume) that large objects were MVCC safe. All of our
applications that work with binary data always use Large Objects.
Sincerely,
Joshua D. Drake
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to majordomo@xxxxxxxxxxxxxx)
--
Your PostgreSQL solutions company - Command Prompt, Inc. 1.800.492.2240
PostgreSQL Replication, Consulting, Custom Programming, 24x7 support
Managed Services, Shared and Dedicated Hosting
Co-Authors: plPHP, plPerlNG - http://www.commandprompt.com/
---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match
