(1) Why are you posting on the pgAdmin support list? Is the problem happening inside pgAdmin?
(2) Just a wild guess… I've not seen this with Postgres, but with in past experience with another database system we were getting NaNs caused by users pasting text into our custom app. As I recall vaguely, this happened typically when copying from their email app. And only on MS Windows computers. Also, Windows seems susceptible to users inputting crazy values involving holding down the Control key. Anyways, I suggest checking the keystroke-filters and data-validation you may have on inputs to the data in question. --Basil Bourque On Nov 18, 2013, at 08:06, Deven Thaker <devenmtha...@gmail.com> wrote: > Hi, > One of the columns of table is getting populated with NaN. When i checked all > scripts which updates this table, found that we never do any division but > still it populates NaN values in the column (double precision) . Surprisingly > behavior is very random and difficult to reproduce. Any pointer, help would > be appreciated > > Environment > Postgre version 9.1 > Windows 7.0
