From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Arturas Mazeika <mazeika(at)gmail(dot)com>, Dave Page <dpage(at)pgadmin(dot)org>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Date: | 2010-11-09 15:31:49 |
Message-ID: | 18124.1289316709@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
> well the usually problem is that it is fairly easy to get large (several
> hundred megabytes) large bytea objects into the database but upon
> retrieval we tend to take up to 3x the size of the object as actual
> memory consumption which causes us to hit all kind of limits(especially
> on 32bit boxes).
It occurs to me that one place that might be unnecessarily eating
backend memory during pg_dump is encoding conversion during COPY OUT.
Make sure that pg_dump isn't asking for a conversion to some other
encoding than what the database uses. I think the default is to avoid
conversion, so this might be a dead end --- but if for instance you
had PGCLIENTENCODING set in the client environment, it could bite you.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2010-11-10 04:23:50 | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |
Previous Message | Kevin Grittner | 2010-11-09 14:47:19 | Re: BUG #5735: pg_upgrade thinks that it did not start the old server |