Thread: Re: [BUGS] Small bug in union
> Thomas, we now get:
> select usesysid from pg_user union select null ;
> ERROR: type id lookup of 0 failed
> which not good either. Can you address this issue?
I'm almost back on-line (I hope) after massive hacker activity took out
the alumni pop server at Caltech. From looking through the hackers
mhonarc archive (hmm, don't much like that name "hackers" anymore; it's
cost us a _lot_ at work and taken me out of Postgres for more than a
month :( I see two issues for me to look at: the one above and the one
from Brett regarding a core dump from a mal-formed query. Will look at
both.
I have some additional patches in the parser area which continue the
type matching/coersion work from the last two months.
I've got patches to put 64-bit integers into the backend; they should
work for Alphas and at least some gcc-compiled 32-bit machines, but
we'll need beta testers to help get the configuration for our other
supported platforms. Once we have that for v6.4, we can also use this
type internally to implement additional types like numeric() and
decimal().
All mail sent to me from June 12 to now has been lost (I lost access to
the pop server and procmail went away, and so my .forward file reference
to procmail was broken and unfixable). It is not yet fixed, but should
be in a day or so. Talk to you then. In the meantime, I will be looking
at the mhonarc archives to keep up (great feature scrappy!)...
- Tom
> > Thomas, we now get: > > select usesysid from pg_user union select null ; > > ERROR: type id lookup of 0 failed > > which not good either. Can you address this issue? ` > > I'm almost back on-line (I hope) after massive hacker activity took out Yea, that is on my list too. One of us will have it fixed for 6.4. The rest sounds good to me. I am not particularly happy with 'hackers' name either. -- Bruce Momjian | 830 Blythe Avenue maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026 + If your life is a hard drive, | (610) 353-9879(w) + Christ can be your backup. | (610) 853-3000(h)
Aww. Hackers is a great name. Devel might be more appropriate, but hackers isn't so bad. On Tue, 7 July 1998, at 14:47:08, Bruce Momjian wrote: > Yea, that is on my list too. One of us will have it fixed for 6.4. The > rest sounds good to me. I am not particularly happy with 'hackers' name > either. > > > -- > Bruce Momjian | 830 Blythe Avenue > maillist@candle.pha.pa.us | Drexel Hill, Pennsylvania 19026 > + If your life is a hard drive, | (610) 353-9879(w) > + Christ can be your backup. | (610) 853-3000(h) >
Brett McCormick <brett@work.chicken.org> writes: > Aww. Hackers is a great name. Devel might be more appropriate, but > hackers isn't so bad. My two cents: "hackers" != "crackers". "Hacker" is an ancient and honorable term for a dedicated programmer, and the PostgreSQL group ought to wear it proudly. The sort of common thieves and vandals who attacked Caltech's system don't deserve the name "hacker"; that crowd is trying to appropriate a term they don't have the right to aspire to. Bad enough that these low-lifes cause us everyday grief, but to steal the hacking community's self-label is an intolerable insult. Don't give in to it. BTW, if you somehow are not familiar with the history of the term "hacker", you might care to visit the Jargon File (try http://sagan.earthspace.net/jargon/), and/or Eric Raymond's page about hacker history and culture (http://tuxedo.org/~esr/faqs/index.html). regards, tom lane
> BTW, if you somehow are not familiar with the history of the term > "hacker", you might care to visit the Jargon File > (try http://sagan.earthspace.net/jargon/), and/or Eric Raymond's > page about hacker history and culture > (http://tuxedo.org/~esr/faqs/index.html). Actually, for some reason we used to use the term (circa mid '70s) to refer to an unaccomplished, undisciplined coder. Sort of like a bad golfer is called a hacker (you know, hacking and slashing at the ball). I haven't found the usage in anything recent though, and the folks who answered my mail at jargon hadn't heard of that usage either (boy, I must have way too much time on my hands...). Still have trouble applying the term to coders with skill :) - Tom