| From: | "George Armhold" <armhold(at)cs(dot)rutgers(dot)edu> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: trouble migrating from 6.3.2 (IRIX) to 7.0.2 (Linux) |
| Date: | 2000-11-24 17:43:38 |
| Message-ID: | 004701c0563e$14084020$a974bf18@KLAMATH |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Earlier in the week I was having problems moving from PG 6.3.2 under IRIX to
version 7.0.2 under Linux. I noticed that pg_dump was creating bogus
(negative value) entries for varchar fields that were initiallly created
with no maximum length constraint. Tom Lane suggested the following:
> It was and is, but it looks like 6.3.2's pg_dump did the wrong thing
> with 'em. If you know that's how these fields were created, I'd say
> that manually removing the (-5) from the table declarations is the
> way to go.
This fixed most of the problems. The one other thing I had to do was rename
a field "offset" to "my_offset" throughout all my tables. Apparently this
is a reserved word in the current version? I still have some more testing
to do, but I seem to have things working now. Thanks to the group, and Tom
Lane in particular.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-11-24 17:47:52 | Re: trouble migrating from 6.3.2 (IRIX) to 7.0.2 (Linux) |
| Previous Message | Tom Lane | 2000-11-24 17:22:12 | Re: Hung backends |