Problems upgrading from 8.2 to 8.3

We have found some unpleasant bugs in 8.3 server which could lead to server hangup so our clients are still on 8.2.

Please provide a complete list of your problems with 8.3 that force you to continue using 8.2, that is important for our developers.

Clearing autocomplete cache
XML deserialization

And I can not fond topic about our server cluster problem. We actually managed to keep it under control in our office, but it is dangerous to install it to our clients without proper supervision.

Also we have found some bugs which make platform to crash without any error and it is very hard to reproduce. It may happen one time out of 100 attempts.

Also looking forward to taxi interface enhancements. We like the idea, but it lack of refinement still. When 8.3.4 will be available for us to download?

I found these two, are they still actual?
PostgreSQL collation error
10061 No connection could be made because the target machine actively refused it

Please report the problems that you have found. Configure logcfg.xml and provide logs also. If you like to make this information available for partners only, you can use Partner forum for that.

Here is what I suppose developers will ask to present in logcfg.xml:

<?xml version="1.0"?>
<config xmlns=http://v8.1c.ru/v8/tech-log>
  <dump location=C:\dumps create="true" type="3" prntscrn="false"/>
  <log location=C:\logs history="48">
    <event>
      <eq property="name" value="PROC"/>
    </event>
    <event>
      <eq property="name" value="CONN"/>
    </event>
    <event>
      <eq property="name" value="EXCP"/>
    </event>
    <event>
      <eq property="name" value="CALL"/>
    </event>
    <event>
      <eq property="name" value="SCALL"/>
    </event>
    <event>
      <eq property="name" value="SESN"/>
    </event>
    <property name="Context">
      <event>
        <eq property="name" value=""/>
      </event>
    </property>
    <property name="all"/>
  </log>
</config>