Re: Schema version management - Mailing list pgsql-hackers

From Joel Jacobson
Subject Re: Schema version management
Date
Msg-id CAASwCXcLBQkxdd48kU-CfnuN6vy_-oatwz14iRcs+AiObT=0pA@mail.gmail.com
Whole thread Raw
In response to Re: Schema version management  (Robert Haas <robertmhaas@gmail.com>)
Responses Re: Schema version management  (Gurjeet Singh <singh.gurjeet@gmail.com>)
List pgsql-hackers
On Thu, Jul 5, 2012 at 2:38 AM, Robert Haas <robertmhaas@gmail.com> wrote:
My vote is - when there's an overloaded function, put each version in
its own file.  And name the files something like
functionname_something.sql.  And just document that something may not
be entirely stable.

I would agree that's better if the dump order isn't deterministic.

However, it looks like an easy fix to make the dump order deterministic:

If the dump order is deterministic, I think its cleaner to put all versions in the same file.

Benefits:
+ Pretty looking filename
+ Same file structure for all object types, no special exception for functions

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Query from VMWare re use of PostgreSQL in new TPC-V benchmark
Next
From: Gurjeet Singh
Date:
Subject: Re: Schema version management