Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...

From: "Chris Travers" <chris(at)travelamericas(dot)com>
To: "Randolf Richardson" <rr(at)8x(dot)ca>, <pgsql-general(at)postgresql(dot)org>
Subject: Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...
Date: 2003-11-29 00:34:02
Message-ID: 002001c3b610$836f7e80$6444053d@SAMUEL
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-advocacy pgsql-general

Randolf Richardson Wrote:
> 2. Moving to table spaces (PostgreSQL version 8 maybe?) rather
> than just storing a whole bunch of files in a single directory. Oracle's
> implementation is nice because tables, indexes, etc., can span multiple
> table spaces, and there are great performance optimization and scalability
> advantages that otherwise just aren't possible without them. I read in
> another thread (approx. 2 months old) earlier this evening that some folks
> would like to see OIDs deprecated, and if this is the case then the sub-
> directories under "base/" will obviously need a different naming
mechanism,
> so instead of re-thinking this perhaps it would be a good opportunity for
> the PostgreSQL team to look at the possibility of implementing things
> within table spaces.

I believe this is being worked on also.

>
> > Anyway one additional thought I had was that it should be possible to
> > write parsers for text files in PL/PERLu and then plug those in as
> > views. In this way, files such as /etc/passwd or even /var/log/messages
> > could be used as if they were tables in the database.
<SNIP>
> A very interesting idea, but my feeling is that pure PERL is best
> suited for dealing with flat text files.

True,. and I use it for that (see my project at
http://sourceforge.net/projects/fwreport) However the ability to take a
similar parser and then use it to present the same information to a RDBMS
would then provide some additional flexibility, as you could use the RDBMS
for managing the query interface to the files. Not very useful if you only
want to see the same files the same way every time, but very useful if you
need to extract different information from them.

>
> > Next question-- any ideas how one could generate something like MySQL's
> > heap tables (maybe in shared memory?) within PostgreSQL?
>
> I have no idea. Anyone else?
>
> --
> Randolf Richardson - rr(at)8x(dot)ca
> Vancouver, British Columbia, Canada
>
> Please do not eMail me directly when responding
> to my postings in the newsgroups.
>
> ---------------------------(end of broadcast)---------------------------
> TIP 3: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>
>

In response to

Responses

Browse pgsql-advocacy by date

  From Date Subject
Next Message Randolf Richardson 2003-11-29 01:12:43 Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...
Previous Message Randolf Richardson 2003-11-29 00:16:07 Re: PostgreSQL Advocacy, Thoughts and Comments

Browse pgsql-general by date

  From Date Subject
Next Message Randolf Richardson 2003-11-29 01:12:43 Re: PostgreSQL, MySQL, etc., was Re: PostgreSQL is much faster than MySQL, only when...
Previous Message Randolf Richardson 2003-11-29 00:27:37 Re: ip of the user doing an insert