From: | "Markus Wollny" <Markus(dot)Wollny(at)computec(dot)de> |
---|---|
To: | "Oleg Bartunov" <oleg(at)sai(dot)msu(dot)su> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Ways to speed up dump&reload |
Date: | 2005-02-21 12:36:59 |
Message-ID: | 2266D0630E43BB4290742247C891057502B9D6C8@dozer.computec.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Oleg,
Yes, thanks - I have installed this patch as soon as it became available. Concerning my largest database, I haven't yet migrated that to tsearch2 - it's still tsearch1-based, so I intend to drop ts1 before the last dump, reload the database with PostgreSQL 8.0.1 and deploy tsearch2 after that. I was thinking more in terms of what would be the optimum settings for things like workmem during reload and creation of the indices - as there's not much else going on at this point of time, it might be worthwhile to use some settings which allocate all available resources to just this task.
Kind regards
Markus
-----Original Message-----
From: Oleg Bartunov [mailto:oleg(at)sai(dot)msu(dot)su]
Sent: Mon 2/21/2005 11:15
To: Markus Wollny
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] Ways to speed up dump&reload
Markus,
have you read updated http://www.sai.msu.su/~megera/postgres/gist/tsearch/V2/docs/tsearch-V2-intro.html
about regprocedure_7.4.patch.gz and regprocedure_update.sql ?
Oleg
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Browne | 2005-02-21 12:45:25 | Re: Scalability with large numbers of tables |
Previous Message | Christopher Browne | 2005-02-21 12:35:28 | Re: Ways to speed up dump&reload |