[HACKERS] Why is pg_dump using INSERTs instead of COPYs?

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

Re: [HACKERS] Why is pg_dump using INSERTs instead of COPYs?

Am Mittwoch, 31. März 2004 13:14 schrieb Tony Reina: 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

Re: [HACKERS] Why is pg_dump using INSERTs instead of COPYs?

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

Re: [HACKERS] Why is pg_dump using INSERTs instead of COPYs?

Tony and Bryn Reina [EMAIL PROTECTED] writes: For the actual command, I'm just saying 'pg_dump -d dbname dboutput.sql' -d is the --inserts switch. regards, tom lane ---(end of broadcast)--- TIP 9: the planner will ignore