From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Ross J(dot) Reedstrom" <reedstrm(at)wallace(dot)ece(dot)rice(dot)edu> |
Cc: | Adriaan Joubert <a(dot)joubert(at)albourne(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [HACKERS] Re: bit types |
Date: | 2000-03-01 19:23:27 |
Message-ID: | 200003011923.OAA13408@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > > The bit-type that is in contrib is useless as it stands. Those are
> > > only C-routines to implement the functionality, and there are none of
> > > the SQL functions to actually make these usable. This really needs to be
> > > integrated with postgres proper. I don't know how to go about this and
> > > that is why I asked for help. I'm prepared to do whatever SQL function
> > > definitions are needed, do the regression tests etc. Would it be better
> > > to go back to the hackers mailing list to ask for help? Has this missed
> > > 7.0 now? If so, we'd better remove the bit-type from contrib.
> >
> > I clearly dropped the ball on this one. Don't think it can go into 7.0
> > because it would require catalog changes/initdb. However, I would like
>
> Hmm, I thought the hard and fast rule was no initdb _after_ release. Surely
> this sort of thing is what beta (especially beta1) is for?
No, we usually avoid initdb if at all possible during beta. A new data
type is not enough reason for it.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2000-03-01 19:28:02 | Re: [HACKERS] Re: bit types |
Previous Message | Bruce Momjian | 2000-03-01 19:13:11 | Re: [HACKERS] patch for plperl Makefile.PL |