Re: pg_upgrade & tablespaces

From: Joseph Kregloh <jkregloh(at)sproutloud(dot)com>
To: John R Pierce <pierce(at)hogranch(dot)com>
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: pg_upgrade & tablespaces
Date: 2013-12-23 14:50:31
Message-ID: CAAW2xfcJBWzo8UiLu3S-4tbemRNGqPEo_--RG2LxzQBEuqxm3w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

On Fri, Dec 20, 2013 at 7:42 PM, John R Pierce <pierce(at)hogranch(dot)com> wrote:

> On 12/20/2013 4:14 PM, Adrian Klaver wrote:
>
>>
>> Personally I would say at this point the relationships between versions
>> are so confused it would seem best to start from scratch.
>>
>
> the 80 tablespaces aren't helping this one bit.
>
>
> I am really curious what lead to creating that many tablespaces? reminds
> me of 1990s Oracle databases where disks were small and you used lots of
> them, and spread your tables and indexes across many different
> drives/mirrors because the raid at the time had performance bottlenecks.
>
>
>
Well the original architect started out in the 80s with banking databases
they just kept that model without revisiting if it works well or not, that
might explain it a little bit. But also given the size of our tables we use
the physical disks and filesytem advantages to improve speed and
performance of the application, but not as often as I would like. We have a
pretty big database.

-Joseph

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message markus.holmberg 2013-12-23 15:48:55 FATAL: index contains unexpected zero page at block
Previous Message Joseph Kregloh 2013-12-23 14:45:28 Re: pg_upgrade & tablespaces

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2013-12-23 15:26:49 Re: preserving forensic information when we freeze
Previous Message Joseph Kregloh 2013-12-23 14:45:28 Re: pg_upgrade & tablespaces