Thread: delete -> copy in -> WAL problem..?

Could use some insight on this one...

We have TWO machines running postgres: one is for
"real-time" data (registrations, order taking, sessions)
and the other is for "non real time" data (content
management, reporting, etc.).

The databases are identical - all 60 tables.  The application
knows which one to use when.   Nightly, we run a cron that \copy's out
the 10 "real-time" tables.  The data is moved to the 2nd machine
and uploaded like this:
    delete from [table];    copy [table] from [table].txt    .. etc.

This has worked well for us - the reporting database
can crunch away on all kinds of reports all day without
affecting the site.

Recently, I've noticed that, during this "copy in" process
(and the subsequent vacuum), the WAL files grow TREMENDOUSLY
in number - a thousand of them.  What's causing this?  Should
I vacuum each table separately after the delete/copy in?
Do I need to force "checkpoints"?

Thanks in advance.

"Mike Biamonte" <mike@dbeat.com> writes:
> Recently, I've noticed that, during this "copy in" process
> (and the subsequent vacuum), the WAL files grow TREMENDOUSLY
> in number - a thousand of them.  What's causing this?

Update.  7.1.3 and later don't do this.
        regards, tom lane