| From: | Joel Jacobson <joel(at)trustly(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Schema version management |
| Date: | 2012-07-05 07:15:35 |
| Message-ID: | CAASwCXcLBQkxdd48kU-CfnuN6vy_-oatwz14iRcs+AiObT=0pA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 5, 2012 at 2:38 AM, Robert Haas <robertmhaas(at)gmail(dot)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:
http://archives.postgresql.org/pgsql-hackers/2012-07/msg00232.php
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Gurjeet Singh | 2012-07-05 08:04:45 | Re: Schema version management |
| Previous Message | Craig Ringer | 2012-07-05 05:33:41 | Query from VMWare re use of PostgreSQL in new TPC-V benchmark |