Re: Modifying COPY TO - Mailing list pgsql-hackers

From Stephen Frost
Subject Re: Modifying COPY TO
Date
Msg-id 20050225230339.GA10437@ns.snowman.net
Whole thread Raw
In response to Modifying COPY TO  ("Dave Held" <dave.held@arrayservicesgrp.com>)
List pgsql-hackers
* Dave Held (dave.held@arrayservicesgrp.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

pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Modifying COPY TO
Next
From: "Jim C. Nasby"
Date:
Subject: Re: idea for concurrent seqscans