| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | dan(at)langille(dot)org |
| Cc: | Sean Chittenden <sean(at)chittenden(dot)org>, pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: 7.1->7.2 data import timestamp problems |
| Date: | 2002-02-23 19:53:36 |
| Message-ID: | 200202231953.g1NJrar00668@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
> Sean: you are on the same track I am. Yes, I found 9 such values in a
> timestamp field. I corrected the data, exported, and imported into 7.2.
> All went well[1].
>
> Now my concern is how the value 'current' found its way into a timestamp
> field.... I'm looking at the application.
I have seen other reports of this. Did anyone realized 'current' could
be stored in the database? I remember discussion about it but I didn't
realize anyone actually used it.
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dan Langille | 2002-02-23 20:14:53 | Re: 7.1->7.2 data import timestamp problems |
| Previous Message | Tom Lane | 2002-02-23 19:50:35 | Re: 7.1->7.2 data import timestamp problems |