From: | Sean Davis <sdavis2(at)mail(dot)nih(dot)gov> |
---|---|
To: | schen(at)graciousstyle(dot)com |
Cc: | postgresql-general mailing list <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: postgresql 8.0 advantages |
Date: | 2005-02-25 14:53:09 |
Message-ID: | 0df3fd3f2c11d351f4b2e73419dc5667@mail.nih.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs pgsql-general |
On Feb 25, 2005, at 9:41 AM, Si Chen wrote:
> Hello.
>
> I read the PostgreSQL 8.0 "What's New" page
> (http://www.postgresql.org/docs/whatsnew) and wasn't sure whether
> version 8.0 is significantly faster, more scalability, or more stable
> than versions 7.4? I remember big speed improvements between 7.3 and
> 7.4. It seems the biggest advantage of version 8.0 is being able to
> run in Windows.
> Is that true?
I like programming in perl and the new pl/perl adds a totally new
dimension to databasing. For example, the dbi-link
(http://pgfoundry.org/projects/dbi-link/) project allows you to create
a schema within your database that mirrors another data source (any
data sources available via perl DBI). You could have an XML file
served from the web as a set of tables in one schema, a mysql database
as a second schema, and a set of csv files in a directory as a third
schema, all with views within Postgres that allow query, update,
delete, etc. Other projects such as this are likely to spring up, I
would imagine. Performance characteristics aside (which I will leave
to others to comment about), I have found the pl/perl improvements well
worth the switch.
Sean
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-02-25 16:15:15 | Re: postgresql 8.0 advantages |
Previous Message | Si Chen | 2005-02-25 14:41:42 | postgresql 8.0 advantages |
From | Date | Subject | |
---|---|---|---|
Next Message | Havasvölgyi Ottó | 2005-02-25 15:09:40 | Manipulating a dataset on the client side |
Previous Message | Lonni J Friedman | 2005-02-25 14:43:10 | Re: multiple runs of the same query cause out of memory - WAS [Re: capturing/viewing sort_mem utilization on a per query basis] |