Re: pg_restore and FK constraints with large dbs

Hi ow,

When your using expensive support, like this email list, technical
replies can take some time.
Perhaps those who can help you are on the other side of the globe and
are sleeping.
Or maybe they busy trying to make a living.

Please be patient.
If you do not recieve a reply I suggest you politely re-post you question.

If all this is not fast enough for you I recommend finding a Postgresql
consultant who
is happy to be on call all day and all night for you.

There are several Postgresql consultant's on these lists, you could post
a request seeking their services.

I'm not trying to upset anyone just trying to help you get an answer for
your issues.

Thanks
Kind regards
Rudi.

ow wrote:

>--- ow <oneway_111(at)yahoo(dot)com> wrote:
>
>
>>Perhaps I should clarify.
>>
>>First, I ran pg_dump to extract schema and data *together*. Then I ran
>>pg_restore to restore the db. It took about 1 hour to create tables and copy
>>the data, then about 40 min to create indexes, then pg_restore spent 4.5
>>hours
>>checking one (1) FK constraint (80M table with FKs against 20K table with
>>PKs)
>>
>>4.5 hours to check one FK constraint - this is what I meant by bad
>>performance.
>>I'm looking for a way to suspend FK checks since data is coming from pg_dump
>>and, hence, it's clean.
>>
>>
>>
>
>No solution? Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Protect your identity with Yahoo! Mail AddressGuard
>http://antispam.yahoo.com/whatsnewfree
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>

ow wrote:

>--- ow <oneway_111(at)yahoo(dot)com> wrote:
>
>
>>Perhaps I should clarify.
>>
>>First, I ran pg_dump to extract schema and data *together*. Then I ran
>>pg_restore to restore the db. It took about 1 hour to create tables and copy
>>the data, then about 40 min to create indexes, then pg_restore spent 4.5
>>hours
>>checking one (1) FK constraint (80M table with FKs against 20K table with
>>PKs)
>>
>>4.5 hours to check one FK constraint - this is what I meant by bad
>>performance.
>>I'm looking for a way to suspend FK checks since data is coming from pg_dump
>>and, hence, it's clean.
>>
>>
>>
>
>No solution? Thanks
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>__________________________________
>Do you Yahoo!?
>Protect your identity with Yahoo! Mail AddressGuard
>http://antispam.yahoo.com/whatsnewfree
>
>---------------------------(end of broadcast)---------------------------
>TIP 4: Don't 'kill -9' the postmaster
>
>
>