From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Miguel Ramos <org(dot)postgresql(at)miguel(dot)ramos(dot)name> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_restore out of memory |
Date: | 2016-07-13 22:42:51 |
Message-ID: | 5407.1468449771@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
I wrote:
> I'm still suspicious that this might be some sort of NOTICE-processing-
> related buffer bloat. Could you try loading the data with the server's
> log_min_messages level cranked down to NOTICE, so you can see from the
> postmaster log whether any NOTICEs are being issued to the pg_restore
> session?
BTW, I experimented with that theory by creating a table with a BEFORE
INSERT trigger function that emits a NOTICE, and then making pg_restore
restore a lot of data into it. I could not see any memory growth in
the pg_restore process. However, I was testing 9.1.22, not 9.1.8.
Also, some of the misbehaviors we've discovered along these lines have
been timing-sensitive, meaning that the problem might or might not
reproduce for another person even with the same software version.
Are you running pg_restore locally on the same machine as the server,
or across a network --- and if the latter, how fast is the network?
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2016-07-14 00:06:33 | Re: postgresql "init script" for postgres 9.2.15 |
Previous Message | Patrick B | 2016-07-13 22:31:56 | Tracking IO Queries |