Re: Why is pg_dump using INSERTs instead of COPYs?

From: "Tony and Bryn Reina" <reina_ga(at)hotmail(dot)com>
To: "Peter Eisentraut" <peter_e(at)gmx(dot)net>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Why is pg_dump using INSERTs instead of COPYs?
Date: 2004-03-31 13:42:46
Message-ID: BAY8-DAV15RAcryMTvW0000fcd5@hotmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> > I've got a database running PostgreSQL 7.4.2 on Fedora Linux. In the
> > past, pg_dump would dump database backups using COPY to restore the
> > data. This time it appears that it has individual INSERTs for each
> > tuple. Perhaps I'm missing this in the latest documentation, but I
> > thought COPY was the default unless the --inserts switch is declared.
>
> This is still the case.
>
> > Can anyone think of why I'd be getting INSERTs?
>
> Shell aliases perhaps.

No. I just re-checked my aliases in the shell. Nothing for pg_dump.

I'm sure the answer is no, but are there any postgres-specific preference
files that may be causing the behavior (perhaps something I'm missing in
postgresql.conf)?

For the actual command, I'm just saying 'pg_dump -d dbname > dboutput.sql'
Nothing fancy.

-Tony

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-03-31 15:23:10 Re: Why is pg_dump using INSERTs instead of COPYs?
Previous Message Peter Eisentraut 2004-03-31 12:35:15 Re: Why is pg_dump using INSERTs instead of COPYs?