Re: Schema version management

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Joel Jacobson <joel(at)trustly(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Schema version management
Date: 2012-07-14 09:25:39
Message-ID: 1342257939.28562.5.camel@vanquo.pezone.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On lör, 2012-07-14 at 10:41 +0200, Joel Jacobson wrote:
> On Fri, Jul 13, 2012 at 9:41 PM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>
> > Personally, I hate this proposed nested directory structure. I would
> > like to have all objects in one directory.
> >
> > But there is a lot of "personally" in this thread, of course.
>
>
> Why do you hate it?
>
> It's a bit like saying,
> - I hate database normalization, better to keep all rows in one single
> table.
> or even,
> - I hate directories.

To a certain extent, yes, I hate (excessive use of) directories.

> I have thousands of objects, it would be a total mess to keep them all in a
> single directory.

Thousands of objects could be a problem, in terms of how the typical
file system tools scale. But hundreds or a few thousand not
necessarily. It's easy to browse, filter, and sort using common tools,
for example.

> Using a normalized directory structure makes sense for the SCM use-case,

If there is a theory of "normalization" for hierarchical databases, I
don't know it but would like to learn about it.

> I haven't seen any projects where all the files are kept in one directory.

Well, of course everyone uses directories in moderation. But you might
want to take a look at the gcc source code. You'll love it. ;-)

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Cédric Villemain 2012-07-14 09:33:13 Re: pg_prewarm
Previous Message Joel Jacobson 2012-07-14 08:41:21 Re: Schema version management