Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 104C32E0050 for ; Wed, 19 Mar 2008 16:27:14 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 75504-02 for ; Wed, 19 Mar 2008 16:27:04 -0300 (ADT) Received: from mx3.hub.org (mx3.hub.org [206.223.169.73]) by postgresql.org (Postfix) with ESMTP id 808DE2E002F for ; Wed, 19 Mar 2008 16:27:07 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.5 Received: from owa.bzzagent.com (exch.bzzagent.com [66.152.196.38]) by mx3.hub.org (Postfix) with ESMTP id 15DE0380A10 for ; Wed, 19 Mar 2008 16:27:07 -0300 (ADT) Received: from EXCHENT01.bzzagent.lan ([172.16.92.24]) by owa.bzzagent.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 19 Mar 2008 15:27:04 -0400 Received: from 172.16.0.230 ([172.16.0.230]) by EXCHENT01.bzzagent.lan ([172.16.92.24]) via Exchange Front-End Server owa.bzzagent.com ([192.168.1.22]) with Microsoft Exchange Server HTTP-DAV ; Wed, 19 Mar 2008 19:27:03 +0000 User-Agent: Microsoft-Entourage/12.0.0.071130 Date: Wed, 19 Mar 2008 15:27:00 -0400 Subject: Re: pg_restore failing with "ERROR: out of memory" From: Aaron Brown To: Tom Lane CC: Message-ID: Thread-Topic: [ADMIN] pg_restore failing with "ERROR: out of memory" Thread-Index: AciJ9dDev0rIkWeoQaWI+Yt0Hw9VywAAWL+C In-Reply-To: <17818.1205954221@sss.pgh.pa.us> Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3288785220_33457669" X-OriginalArrivalTime: 19 Mar 2008 19:27:04.0039 (UTC) FILETIME=[3643A770:01C889F7] X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=1.82 tagged_above=0 required=5 tests=AWL=0.000, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=1.819 X-Spam-Level: * X-Archive-Number: 200803/149 X-Sequence-Number: 28632 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3288785220_33457669 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable I agree that they =B3should=B2. Unfortunately, nothing about slony is simple, in my experience. On 3/19/08 3:17 PM, "Tom Lane" wrote: > Aaron Brown writes: >> > Yes, it kind of needs to be data only since I am pulling from a sloniz= ed >> > database. My experience has been if you don=B9t load the schema first w= ith a >> > schema from slony1_extract_schema.sh, we end up with all the slony tri= ggers >> > and crap in the dump. If there is a better way of doing this, I=B9m >> > definitely all ears. >=20 > Well, you'd need to take that up on the Slony lists, but I'd say that > Slony definitely ought to provide a better export mechanism than forcing > you to use a standard data-only dump. At minimum they should teach that > script to emit two separate files: one to load before the data and one > after. Building the indexes and FK constraints on already-loaded data > is a heck of a lot faster. >=20 > regards, tom lane >=20 >=20 ------------------------------------------------------- Aaron Brown, Systems Engineer BzzAgent, Inc. | www.bzzagent.com abrown@bzzagent.com | 617.451.2280 -------------------------------------------------------=20 --B_3288785220_33457669 Content-type: text/html; charset="ISO-8859-1" Content-transfer-encoding: quoted-printable Re: [ADMIN] pg_restore failing with "ERROR: out of memory"= I agree that they “should”.   Unfortu= nately, nothing about slony is simple, in my experience.


On 3/19/08 3:17 PM, "Tom Lane" <tgl@sss.pgh.pa.us> wrote:
Aaron Brown <abrown@bzz= agent.com> writes:
> Yes, it kind of needs to be data only since I am pulling from a sloniz= ed
> database.  My experience has been if you don’t load the sch= ema first with a
> schema from slony1_extract_schema.sh, we end up with all the slony tri= ggers
> and crap in the dump.  If there is a better way of doing this, I&= #8217;m
> definitely all ears.

Well, you'd need to take that up on the Slony lists, but I'd say that
Slony definitely ought to provide a better export mechanism than forcing you to use a standard data-only dump.  At minimum they should teach th= at
script to emit two separate files: one to load before the data and one
after.  Building the indexes and FK constraints on already-loaded data=
is a heck of a lot faster.

            &nb= sp;           regards= , tom lane




-------= ------------------------------------------------
Aaron Brown, Systems Engineer
BzzAgent, Inc. | www.bzzagent.com
abrown@bzzagent.com | 617.451.2280
-------------------------------------------------------

--B_3288785220_33457669--