Sun Jun 11 05:41:22 PDT 2006
- Previous message: [Slony1-general] Large initial COPY transaction and a possible solution for the provider
- Next message: [Slony1-general] Large initial COPY transaction and a possible solution for the provider
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 6/9/2006 5:45 PM, Christopher Browne wrote: > 2. Load the data, and throw reindexing to a separate thread that might > take place concurrently... > > for each table t > deactivate indexes on t > copy data for T > reactivate indexes on t > throw table t to reindexing thread > done This won't work at all. Because the COPY thread's transaction isn't committed yet, any other connection won't see the data to index. Jan -- #======================================================================# # It's easier to get forgiveness for being wrong than for being right. # # Let's break this rule - forgive me. # #================================================== JanWieck at Yahoo.com #
- Previous message: [Slony1-general] Large initial COPY transaction and a possible solution for the provider
- Next message: [Slony1-general] Large initial COPY transaction and a possible solution for the provider
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-general mailing list