On Mon, Mar 10, 2014 at 08:12:20PM +0100, Pavel Stehule wrote:
> Remember pg_upgrade is using pg_dump, which then connecting to a
> backend, so passing that super-lock mode there is not ideal. The fixes
> in 9.3 improve locking in all user cases, not just upgrades.
>
>
>
> nice
FYI
2014-03-10 20:11 GMT+01:00 Bruce Momjian :
> On Mon, Mar 10, 2014 at 07:40:42PM +0100, Pavel Stehule wrote:
> >
> > >
> > > There were several bottlenecks in this area removed in 9.2 and 9.3.
> > > Unfortunately the worst of those bottlenecks were in the server,
> so they
> > depen
On Mon, Mar 10, 2014 at 07:40:42PM +0100, Pavel Stehule wrote:
>
> >
> > There were several bottlenecks in this area removed in 9.2 and 9.3.
> > Unfortunately the worst of those bottlenecks were in the server, so they
> depend
> > on what database you are upgrading from, and so
> >
> > There were several bottlenecks in this area removed in 9.2 and 9.3.
> > Unfortunately the worst of those bottlenecks were in the server, so they
> depend
> > on what database you are upgrading from, and so won't help you much
> upgrading
> > from 9.1.
>
> Yes, I assume 9.3 will be much bett
On Mon, Mar 10, 2014 at 09:54:36AM -0700, Jeff Janes wrote:
> On Mon, Mar 10, 2014 at 6:58 AM, Pavel Stehule
> wrote:
>
> Hello
>
> I had to migrate our databases from 9.1 to 9.2. We have high number of
> databases per cluster (more than 1000) and high number of tables (indexes)
>
On Mon, Mar 10, 2014 at 6:58 AM, Pavel Stehule wrote:
> Hello
>
> I had to migrate our databases from 9.1 to 9.2. We have high number of
> databases per cluster (more than 1000) and high number of tables (indexes)
> per database (sometimes more than 10K, exceptionally more than 100K).
>
> I seen t
Hello
I had to migrate our databases from 9.1 to 9.2. We have high number of
databases per cluster (more than 1000) and high number of tables (indexes)
per database (sometimes more than 10K, exceptionally more than 100K).
I seen two problems:
a) too long files pg_upgrade_dump_db.sql, pg_upgrade_
