| From: | "Francisco Reyes" <lists(at)stringsutils(dot)com> |
|---|---|
| To: | Jack Orenstein <jack(dot)orenstein(at)hds(dot)com> |
| Cc: | <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: COPY between 7.4.x and 8.3.x |
| Date: | 2008-07-21 20:50:35 |
| Message-ID: | ffc76bbaf910294d79b6736910f55d53@stringsutils.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 4:05 pm 07/21/08 Jack Orenstein <jack(dot)orenstein(at)hds(dot)com> wrote:
> We will now be adding 8.3.x databases to the mix, and will need to
> copy between 7.4.x and 8.3.x in both directions. The datatypes we use
I believe it should work.
Also, one feature I believe started in the 8.X line (8.2?), is the ability
to have a subquery in the copy command to refine what rows you are getting.
> What if we do a binary copy instead?
What do you mean by a binary copy?
pg_dump -Fc?
I think a plain pg_dump and copy will likely be more portable. Specially
going from 8.3 to 7.4.
Why will you keep copying data back and forth?
Not possible to setup a new 8.3, migrate to it and then upgrade the other
7.4 machine to 8.3?
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Emil Pedersen | 2008-07-21 20:59:47 | inconsistent program behavior, fresh eyes needed |
| Previous Message | Jack Orenstein | 2008-07-21 20:05:01 | COPY between 7.4.x and 8.3.x |