> |
> | Could we somehow speed up our initial copy by dropping PK and other
> | indexes during COPY and rebuilding them later ? I tried to do it
> manually
> | after setting up replication but before subscribing but subscription
> also
> | checked for existing pk.
>
> You need the pk to run slony, but you can ditch all your other indices
> and rebuild them later.

I know I need PK to *run* slony, but I also know that loading data first
and then building an index can run an order of magnitude faster than
copying into a table with indexes.

I think the initial COPY time could be much reduced if done in a similar
way to what pg_dump does (i.e DROP PK; TRUNCATE TABLE; COPY ; ALTER TBL
ADD PK)

----------------
Hannu