| From: | zhong ming wu <mr(dot)z(dot)m(dot)wu(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: invalid abstime to timestamp error only on specific date range |
| Date: | 2010-04-27 23:00:49 |
| Message-ID: | u2y9e434c4d1004271600jbe14353er15faa449bcf8391e@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Tue, Apr 27, 2010 at 11:02 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> zhong ming wu <mr(dot)z(dot)m(dot)wu(at)gmail(dot)com> writes:
>
> The closest thing I can find to that in the code is
>
> cannot convert abstime "invalid" to timestamp
Yes this is the message.
There were invalid values in that table at first. Then I deleted
such entries and tried the same query and got the same message.
The query is four table joins but in order to pin-point the problem
I pruned it down to as simple as what I posted originally.
In any case I reloaded the data and on this second pass
I stopped receiving the error. The reloading scripts were
different and I don't know what that did to the reloaded data.
Thanks
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anthony | 2010-04-28 00:45:43 | Re: Storing many big files in database- should I do it? |
| Previous Message | Scott Marlowe | 2010-04-27 22:00:51 | Re: VACUUM FULL vs backup/restore |