On 25 Aug 2001, Doug McNaught wrote:
> > Can someone explain why the addition of a stored procedural language for
> > MySQL made it as a Slashdot headline?
>
> Probably because /. uses MySQL (poor benighted fools ;)
Back when Slashdot was designed, Postgres was crap. We have old versions
we're still getting rid of, and they're the biggest headache in the world.
I've actually used \d and the back-end crashed. Usually this happens when
the database has handled around 15k queries in one session, or someone,
somewhere, even looks in the direction of a row that is anywhere near the
8k limit.
It's very simple. Anything before postgres 7.1 was complete, utter crap.
Slashdot was around way before 7.1, hence mysql.
Personally, I laud their decision. I mean, I've never had "show tables"
crash a mysql database, yet \d (or even a single-table, no where clause
select) can crash the back end of postgres 7.0.3. We can't even do bulk
inserts on these tables (20k rows) because the back end inexplicably dies
before it finishes. I'm talking about insert statements, not postgres
proprietary COPY.
--
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
| Shaun M. Thomas INN Database Programmer |
| Phone: (309) 743-0812 Fax : (309) 743-0830 |
| Email: [EMAIL PROTECTED] AIM : trifthen |
| Web : hamster.lee.net |
| |
| "Most of our lives are about proving something, either to |
| ourselves or to someone else." |
| -- Anonymous |
+-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-+
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/users-lounge/docs/faq.html
