| From: | Anuradha Ratnaweera <anuradha(at)gnu(dot)org> |
|---|---|
| To: | Joel Burton <jburton(at)scw(dot)org> |
| Cc: | bangh <banghe(at)baileylink(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jeremy Buchmann <jeremy(at)wellsgaming(dot)com>, pgsql-admin <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Reason to not upgrade from 6.5 to 7.0 or above |
| Date: | 2001-04-28 12:41:15 |
| Message-ID: | Pine.LNX.4.21.0104281837410.233-100000@presario |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
On Wed, 25 Apr 2001, Joel Burton wrote:
> Is there anything that datetime did that timestamp doesn't?
datetime is provided to ensure compatibility with older releases, although
they are not guranteed to exist in future releases (chapter 3.4 users
guide)
> Could you
>
> pg_dump | sed | psql
>
> to change the datetimes to timestamp?
No. pg_dump will read from the database while psql will modify it and
there can be conflicts. It is safe to
pg_dumpall -c | sed > tmpfile
psql -d template1 -f tmpfile
Anuradha
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Anuradha Ratnaweera | 2001-04-28 12:42:37 | Re: Restoring a pg_dump fails with |
| Previous Message | Anuradha Ratnaweera | 2001-04-28 12:34:00 | Re: 7.1 performance |