Re: pg_restore and FK constraints with large dbs

On Mon, 17 Nov 2003, ow wrote:

> --- Stephan Szabo <sszabo(at)megazone(dot)bigpanda(dot)com> wrote:
> >
> > I assume you're also not modifying the pktable rows (since that would
> > access the fk table based solely on the fk).
>
> I do modify the fk table: inserts and updates (but pk is never updated). Also
> do not delete records.
>
> > Does the multi-field index start with fk or some other field?
> Some other field.
>
> In general, even if I put that additional index and somehow cut down FK
> verification time for 1 constraint to, say, 30 min, does that mean that the
> problem is solved? Tomorrow, someone may come with 800M fk table against 200K
> pk table, or he may have 10 FK constraints like this, etc. How's he going to
> restore db in production environment when there's a problem and time is factor?

Well, I've been trying to deal with the particular case at hand, ie, get
your load in a more reasonable amount of time assuming that you had more
constraints and this was going to be a particular problem for you in the
immediate term. I've mentioned that there's likely to be future
development on the issue in this thread already and that there was a
recent discussion on the topic that occurred a bit late to do anything for
7.4. I can't change the past to suit your desires, sorry, the best I can
do is point you towards getting a solution for the future.