From: | Ants Aasma <ants(at)cybertec(dot)at> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Magnus Hagander <magnus(at)hagander(dot)net> |
Subject: | Re: Further pg_upgrade analysis for many tables |
Date: | 2012-11-10 17:17:34 |
Message-ID: | CA+CSw_vU-f0E3fWRWMXuwEwbaF7VeVv7UY4EXAEgMb_SLggBkA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, Nov 10, 2012 at 7:10 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I am confused why you see a loop. transfer_all_new_dbs() does a
> merge-join of old/new database names, then calls gen_db_file_maps(),
> which loops over the relations and calls create_rel_filename_map(),
> which adds to the map via array indexing. I don't see any file loops
> in there --- can you be more specific?
Sorry, I was too tired when posting that. I actually meant
transfer_single_new_db(). More specifically the profile clearly showed
that most of the time was spent in the two loops starting on lines 193
and 228.
Ants Aasma
--
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2012-11-10 17:18:11 | Re: Further pg_upgrade analysis for many tables |
Previous Message | Bruce Momjian | 2012-11-10 17:15:58 | Re: Further pg_upgrade analysis for many tables |