Last test...
On a new PC I install in this order :
- Windows 7 Pro SP1 x64 French (brand new original DVD)
- postgresql-9.0.4-1-windows_x64.exe (installing with Locale French, Belgium
or default locale, same results)
- jre-6u24-windows-x64
- dbvis_windows-x64_7_1_4.exe
- postgresql-9.0-801.jdbc4.
On Thu, Apr 28, 2011 at 9:53 AM, Carlo Curatolo wrote:
> Last test...
>
> On a new PC I install in this order :
>
> - Windows 7 Pro SP1 x64 French (brand new original DVD)
> - postgresql-9.0.4-1-windows_x64.exe (installing with Locale French, Belgium
> or default locale, same results)
> - jre-6u24
My actual PG 8.4 production server works perfectly and in the reports
correctly errors everywhere (PGAdmin, DBVisualizer, Java applications, EMS
SQL Manager Lite)...
If somebody have an idea...a workaround...a solution...
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/B
Same test but with the 32bits version of PG9
The problem do NOT occurs...
Everything works paerfectly everywhere...
Where I have to post my problem to have a solution ?
--
View this message in context:
http://postgresql.1045698.n5.nabble.com/BUG-5800-corrupted-error-messages-encoding-problem-t
Please keep the list copied. I'm moving this to the pgsql-admin
list (with a blind copy to -bugs), since there is really no hint of
a PostgreSQL bug here, except possibly in terms of how we document
this issue.
Suprabhat Mohapatra wrote:
> Should I send you the sample code that we are using
The following bug has been logged online:
Bug reference: 5996
Logged by: Brian S. Krug
Email address: bk...@usatech.com
PostgreSQL version: 9.0.3
Operating system: Solaris
Description:CURRENT_TIMESTAMP uses often undesired
TRANSACTION_TIMESTAMP, instead of STATEMENT_T
On 04/28/11 12:33 PM, Brian S. Krug wrote:
The following bug has been logged online:
Bug reference: 5996
Logged by: Brian S. Krug
Email address: bk...@usatech.com
PostgreSQL version: 9.0.3
Operating system: Solaris
Description:CURRENT_TIMESTAMP uses often undesired
T
