Re: Uber migrated from Postgres to MySQL

On Wed, Jul 27, 2016 at 07:02:52PM -0400, Alvaro Herrera wrote:
> Patrick B wrote:
> > >
> > > I think it's safe to say that that has absolutely nothing to do
> > > with the size being 3TB. They symptoms you report are a little
> > > thin to diagnose the actual cause.
> >
> > might be... we're using SATA disks... and that's a big problem. But still..
> > the size of the DB is indeed a problem.
>
> Andrew is correct -- the size of the database is not a limitation for
> pg_upgrade. Disk tech is not relevant either. You may run into the
> problem that you don't have enough disk space, but then that is not a
> database or pg_upgrade problem, is it?
>
> Other things might cause issues, but since you haven't actually reported
> the problem, we don't know what is or whether there is any possible fix.
>
> Then again, if you want to report a pg_upgrade failure, I suggest you
> open a thread of your own rather than hijack this one.

You need only minimal disk space when using pg_upgrade --link. I agree
we would like a full bug report so we can find a fix for you.

--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +