| From: | "Matthew T(dot) OConnor" <matthew(at)zeut(dot)net> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Hannu Krosing <hannu(at)tm(dot)ee> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Date: | 2002-09-12 16:09:34 |
| Message-ID: | 200209121209.34668.matthew@zeut.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-patches |
> > The count approach seems definitely the right way, but a check (possibly
> > a slow one) can be probably done without initdb.
>
> We can certainly do the proper fix in 7.4; do we consider this bug
> important enough to do an initdb for 7.3beta2? I don't have a strong
> feeling either way about that.
I think we are too scared of doing initdb during beta...
Initdb during beta should not be evaultated on a per bug basis, but keep a
list of all things that could be fixed and judge if the total of all the
fixes is worth one initdb. Right now off the top of my head I can think of
the split function and this inherited change, are there more?
my two cents...
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2002-09-12 16:15:16 | Re: |
| Previous Message | Bruce Momjian | 2002-09-12 16:04:03 | Re: PGXLOG variable worthwhile? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | scott.marlowe | 2002-09-12 16:23:53 | Re: DROP COLUMN misbehaviour with multiple inheritance |
| Previous Message | Bruno Wolff III | 2002-09-12 15:28:39 | Re: Earth Distance patch |