From: | Aaron Brown <abrown(at)bzzagent(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: pg_restore failing with "ERROR: out of memory" |
Date: | 2008-03-19 19:27:00 |
Message-ID: | C406E144.5B9F%abrown@bzzagent.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I agree that they ³should². Unfortunately, nothing about slony is simple,
in my experience.
On 3/19/08 3:17 PM, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Aaron Brown <abrown(at)bzzagent(dot)com> writes:
>> > Yes, it kind of needs to be data only since I am pulling from a slonized
>> > database. My experience has been if you don¹t load the schema first with a
>> > schema from slony1_extract_schema.sh, we end up with all the slony triggers
>> > and crap in the dump. If there is a better way of doing this, I¹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 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.
>
> regards, tom lane
>
>
-------------------------------------------------------
Aaron Brown, Systems Engineer
BzzAgent, Inc. | www.bzzagent.com
abrown(at)bzzagent(dot)com | 617.451.2280
-------------------------------------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Carol Walter | 2008-03-19 21:21:39 | Empty database creation??? |
Previous Message | Tom Lane | 2008-03-19 19:17:01 | Re: pg_restore failing with "ERROR: out of memory" |