| From: | Stephen Frost <sfrost(at)snowman(dot)net> |
|---|---|
| To: | Dave Held <dave(dot)held(at)arrayservicesgrp(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Modifying COPY TO |
| Date: | 2005-02-25 23:03:39 |
| Message-ID: | 20050225230339.GA10437@ns.snowman.net |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
* Dave Held (dave(dot)held(at)arrayservicesgrp(dot)com) wrote:
> A possibility that I would like to pursue is to keep the staging data
> from the previous day, do a COPY TO, import the new data into
> another staging table with a COPY FROM, then export the fresh
> data with another COPY TO. Then, I can write a fast C/C++
> program to do a line-by-line comparison of each record, isolating
> the ones that have changed from the previous day. I can then
> emit those records in a change file that should be relatively small
> and easy to update. Of course, this scheme can only work if
> COPY TO emits the records in a reliable order.
sort -u old new > changes
?
Stephen
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jim C. Nasby | 2005-02-26 00:03:53 | Re: idea for concurrent seqscans |
| Previous Message | Tom Lane | 2005-02-25 22:56:50 | Re: Modifying COPY TO |