| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Mike Rogers" <temp6453(at)hotmail(dot)com> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: Large PG_DUMPs going into memory? |
| Date: | 2002-05-06 02:26:28 |
| Message-ID: | 28407.1020651988@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-patches |
"Mike Rogers" <temp6453(at)hotmail(dot)com> writes:
> The problem is that whether the database is remote or local [i have tried
> running it on the DB server itself with the same result], it takes up a good
> half gigabyte of RAM for the course of the dump. Why does it load all of
> this into memory on the client machine rather than output it as it comes in.
Use a more recent pg_dump. This is fixed in 7.2.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | smith | 2002-05-06 04:47:52 | Use Postgresql in VB |
| Previous Message | Mike Rogers | 2002-05-06 02:08:37 | Large PG_DUMPs going into memory? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Patrick Macdonald | 2002-05-06 16:02:09 | Python DB API (pgdb.py) patch |
| Previous Message | Mike Rogers | 2002-05-06 02:08:37 | Large PG_DUMPs going into memory? |