Big copy slowdown
Oct 22, 2007 at 8:28 pm
Brian Hurt writes:
Is this a bug in postgres?
Well, if you'd provide enough info for someone else to reproduce it, we
could have a look.
regards, tom lane
: I'm not sure if this is the right forum for this question, so I'll start here and escalate as necessary. One of the things I do a lot is copy large tables from one database to another. I'd started life using pgdump, but this requires I save the whole table into an intermediate file (or play games with pipes). Rather than doing either, I instead wrote a quick script which creates a cursor at the source, and starts schlepping data from one to other. For "small" tables (say, a million rows or
: Hello- I just wanted to close the book on this problem. I first noticed the problem when long copies kept slowing down. It turns out it wasn't a problem with Postgresql at all, as I recreated it with bonnie++ (which explains the long silence on this issue). After doing a lot of sustained I/O, we see I/O wait times climb until we're getting virtually no I/O performance at all, and it doesn't matter if it's Postgresql or bonnie++ doing the I/O. iostat would report that we'd be doing only 2MB/sec,
RE: dramatic slowdown in selects after pg has been runni ng for a while
dramatic slowdown in selects after pg has been running for a while
Copying data from table to table (cloned tables)
Unknown character on copy
psql copy paste failure
Error in using copy command
is it possible to flush / commit / update underlying table during the COPY table FROM 'pipe'
do i need to define a table before importing csv data using copy?
COPY from PGAdmin
Send parameters using Shell script to PostgreSQL
2 of 3
Oct 22, '07 at 7:44p
Nov 26, '07 at 4:09p
2 users in discussion
Brian Hurt (2)
Tom Lane (1)
Groups & Organizations
site design / logo © 2021 Grokbase