From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Fetter <david(at)fetter(dot)org> |
Cc: | pgsql-committers(at)postgresql(dot)org |
Subject: | Re: pgsql: Implement a preliminary 'template' facility for procedural |
Date: | 2005-09-06 02:46:55 |
Message-ID: | 13729.1125974815@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
David Fetter <david(at)fetter(dot)org> writes:
>> For now the template data is hard-wired in proclang.c --- this
>> should be replaced later by a new shared system catalog, but we
>> don't want to force initdb during 8.1 beta.
> Wouldn't beta be the time to do it? I know we define initdb-forcing
> changes to mean a major version bump, but I also thought that beta was
> a time to find the places where such changes make sense. Has there
> been a guarantee that beta means "no initdb" in previous releases?
No, but we avoid initdb after beta1 when we can. Our long-suffering
beta testers don't need to be whacked around unnecessarily.
If something comes along that forces an initdb (for instance, we find
something wrong with ROLEs that can't be fixed without a catalog change)
then I'll think hard about pushing in the additional changes to create a
pltemplate system catalog. But it seemed easier to sell the idea as a
non-initdb-forcing change ...
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | User Dpage | 2005-09-06 07:47:26 | psqlodbc - psqlodbc: Re-enable ANSI/Unicode compilation. |
Previous Message | Michael Glaesemann | 2005-09-06 02:42:34 | Re: pgsql: Implement a preliminary 'template' facility for procedural |