Tom Lane writes:
> Maybe you can duplicate the problem with a synthesized or anonymized
> data set? It's unlikely anybody will spend much time on such a vague
> report as this.
I reloaded the same data set overnight, and I could not reproduce the
error (which was present in one in 3.6 million r
"Dag Lem" writes:
> The effect of this (pretty serious) bug is that I am able to insert a value
> into an integer column and consistently get an entirely different value read
> out later.
> Unfortunately this happens on a large data set (3.6M rows), and I am not
> able to either reproduce with a
The following bug has been logged online:
Bug reference: 5876
Logged by: Dag Lem
Email address: d...@nimrod.no
PostgreSQL version: 9.0.3
Operating system: CentOS release 5.5, i686
Description:Incorrectly reported column value
Details:
The effect of this (pretty seri
