Re: Largeobject Access Controls (r2460)
Tom Lane <tgl@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
To: "Kevin Grittner" <Kevin.Grittner@wicourts.gov>
Cc: "Greg Smith" <greg@2ndquadrant.com>,
"KaiGai Kohei" <kaigai@ak.jp.nec.com>, "Robert Haas" <robertmhaas@gmail.com>, "KaiGai Kohei" <kaigai@kaigai.gr.jp>, "Takahiro Itagaki" <itagaki.takahiro@oss.ntt.co.jp>, pgsql-hackers@postgresql.org, "Jaime Casanova" <jcasanov@systemguards.com.ec>
Date: 2010-01-25T19:46:25Z
Lists: pgsql-hackers
"Kevin Grittner" <Kevin.Grittner@wicourts.gov> writes: > "Kevin Grittner" <Kevin.Grittner@wicourts.gov> wrote: >> Tom Lane <tgl@sss.pgh.pa.us> wrote: >>> Did you happen to notice anything about pg_dump's memory >>> consumption? > I took a closer look, and there's some bad news, I think. The above > numbers were from the ends of the range. I've gone back over and > found that while it dropped about 2.1 GB almost immediately, cache > usage slowly dropped throughout the dump, and bottomed at about 6.9 > GB below baseline. OK, that's still not very scary --- it just means my off-the-cuff estimate of 1:1 space usage was bad. 3:1 isn't that surprising either given padding and other issues. The representation of ArchiveEntries could probably be made a bit more compact ... regards, tom lane