pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedpostgresql 8.0 advantages
11+ messages / 9 participants
[nested] [flat]
* postgresql 8.0 advantages
@ 2005-02-25 14:41 Si Chen <schen@graciousstyle.com>
0 siblings, 2 replies; 11+ messages in thread
From: Si Chen @ 2005-02-25 14:41 UTC (permalink / raw)
To: postgresql-general mailing list <pgsql-general@postgresql.org>
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?
Thanks,
Si Chen
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-25 14:53 Sean Davis <sdavis2@mail.nih.gov>
parent: Si Chen <schen@graciousstyle.com>
1 sibling, 0 replies; 11+ messages in thread
From: Sean Davis @ 2005-02-25 14:53 UTC (permalink / raw)
To: schen@graciousstyle.com; +Cc: postgresql-general mailing list <pgsql-general@postgresql.org>
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
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-25 16:15 Tom Lane <tgl@sss.pgh.pa.us>
parent: Si Chen <schen@graciousstyle.com>
1 sibling, 2 replies; 11+ messages in thread
From: Tom Lane @ 2005-02-25 16:15 UTC (permalink / raw)
To: schen@graciousstyle.com; +Cc: postgresql-general mailing list <pgsql-general@postgresql.org>
Si Chen <schen@graciousstyle.com> writes:
> 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.
There are some speed improvements in 8.0 too, though that wasn't the
main focus of the release cycle. For instance, Lonni Friedman's nearby
thread reports on a case where 8.0 consistently finds a much better
query plan for a complex query than prior releases did, because we fixed
some issues in the GEQO planner module.
regards, tom lane
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-25 17:20 Lonni J Friedman <netllama@gmail.com>
parent: Si Chen <schen@graciousstyle.com>
1 sibling, 0 replies; 11+ messages in thread
From: Lonni J Friedman @ 2005-02-25 17:20 UTC (permalink / raw)
To: schen@graciousstyle.com; +Cc: pgsql-general@postgresql.org
On Fri, 25 Feb 2005 09:20:29 -0800, Si Chen <schen@graciousstyle.com> wrote:
> Thanks!
>
> Is there any documentation on how to upgrade to 8.0?
Dump your DB, install 8.0, reload your DB. Since you'e using RHEL3,
you should use the RPMs and it will be fairly easy.
> Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> database running "in place"? Or should I install 8.0 in another
No, its not.
> directory/machine and then restore the database into it? Are there any
> incompatibilities/modifications to databases from the earlier veresion
> required?
Depends on what kind of data structures you have in the DB
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman netllama@gmail.com
LlamaLand http://netllama.linux-sxs.org
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-25 17:20 Si Chen <schen@graciousstyle.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 2 replies; 11+ messages in thread
From: Si Chen @ 2005-02-25 17:20 UTC (permalink / raw)
To: pgsql-general@postgresql.org
Thanks!
Is there any documentation on how to upgrade to 8.0?
Is it possible to upgrade from 7.4 to 8.0 while keeping a production
database running "in place"? Or should I install 8.0 in another
directory/machine and then restore the database into it? Are there any
incompatibilities/modifications to databases from the earlier veresion
required?
(I am running RHEL3.)
Si Chen
Tom Lane wrote:
>Si Chen <schen@graciousstyle.com> writes:
>
>
>>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.
>>
>>
>
>There are some speed improvements in 8.0 too, though that wasn't the
>main focus of the release cycle. For instance, Lonni Friedman's nearby
>thread reports on a case where 8.0 consistently finds a much better
>query plan for a complex query than prior releases did, because we fixed
>some issues in the GEQO planner module.
>
> regards, tom lane
>
>
>
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-26 09:27 Jeff Davis <jdavis-pgsql@empires.org>
parent: Si Chen <schen@graciousstyle.com>
1 sibling, 1 reply; 11+ messages in thread
From: Jeff Davis @ 2005-02-26 09:27 UTC (permalink / raw)
To: schen@graciousstyle.com; +Cc: PgSQL General List <pgsql-general@postgresql.org>
On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
> Thanks!
>
> Is there any documentation on how to upgrade to 8.0?
>
> Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> database running "in place"? Or should I install 8.0 in another
> directory/machine and then restore the database into it? Are there any
> incompatibilities/modifications to databases from the earlier veresion
> required?
>
You might want to check out Slony-I <http://www.slony.info; for the
purpose of upgrading. Slony is actually a replication engine, but it can
be used to upgrade with little or no downtime. Otherwise, just
dump/upgrade/restore like normal.
As far as compatibility, 8.0 should be mostly backwards compatible.
There may be some minor things that I don't know about, so I recommend
some testing first.
Regards,
Jeff Davis
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-26 21:35 Jim C. Nasby <decibel@decibel.org>
parent: Jeff Davis <jdavis-pgsql@empires.org>
0 siblings, 3 replies; 11+ messages in thread
From: Jim C. Nasby @ 2005-02-26 21:35 UTC (permalink / raw)
To: Jeff Davis <jdavis-pgsql@empires.org>; +Cc: schen@graciousstyle.com, PgSQL General List <pgsql-general@postgresql.org>
On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote:
> On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
> > Thanks!
> >
> > Is there any documentation on how to upgrade to 8.0?
> >
> > Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> > database running "in place"? Or should I install 8.0 in another
> > directory/machine and then restore the database into it? Are there any
> > incompatibilities/modifications to databases from the earlier veresion
> > required?
> >
>
> You might want to check out Slony-I <http://www.slony.info; for the
> purpose of upgrading. Slony is actually a replication engine, but it can
> be used to upgrade with little or no downtime. Otherwise, just
> dump/upgrade/restore like normal.
Has anyone tried moving a database from one location to another on the
HD? I'd like to use slony to minimize downtime, but I'd also like my
data to end up in the same place it is right now when I'm done.
--
Jim C. Nasby, Database Consultant decibel@decibel.org
Give your computer some brain candy! www.distributed.net Team #1828
Windows: "Where do you want to go today?"
Linux: "Where do you want to go tomorrow?"
FreeBSD: "Are you guys coming, or what?"
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-27 02:12 Christopher Browne <cbbrowne@acm.org>
parent: Jim C. Nasby <decibel@decibel.org>
2 siblings, 0 replies; 11+ messages in thread
From: Christopher Browne @ 2005-02-27 02:12 UTC (permalink / raw)
To: pgsql-general@postgresql.org
The world rejoiced as decibel@decibel.org ("Jim C. Nasby") wrote:
> On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote:
>> On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
>> > Thanks!
>> >
>> > Is there any documentation on how to upgrade to 8.0?
>> >
>> > Is it possible to upgrade from 7.4 to 8.0 while keeping a production
>> > database running "in place"? Or should I install 8.0 in another
>> > directory/machine and then restore the database into it? Are there any
>> > incompatibilities/modifications to databases from the earlier veresion
>> > required?
>> >
>>
>> You might want to check out Slony-I <http://www.slony.info; for the
>> purpose of upgrading. Slony is actually a replication engine, but it can
>> be used to upgrade with little or no downtime. Otherwise, just
>> dump/upgrade/restore like normal.
>
> Has anyone tried moving a database from one location to another on the
> HD? I'd like to use slony to minimize downtime, but I'd also like my
> data to end up in the same place it is right now when I'm done.
Yes, that certainly ought to work.
If what you're meaning is that you make a replica that sits in
/opt/VERSION8, and then, once the upgrade is complete, rename that to
/opt/MYDATABASE which was where your version 7.4 DB used to be.
We have copied databases from one server to another by copying the
files; making it work was as easy as making sure we ran "pg_ctl -D
$RIGHT_DIRECTORY start" :-).
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/lisp.html
"I don't know why, but first C programs tend to look a lot worse than
first programs in any other language (maybe except for FORTRAN, but
then I suspect all FORTRAN programs look like `firsts')" -- Olaf Kirch
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-27 10:58 Julian Scarfe <julian@avbrief.com>
parent: Tom Lane <tgl@sss.pgh.pa.us>
1 sibling, 0 replies; 11+ messages in thread
From: Julian Scarfe @ 2005-02-27 10:58 UTC (permalink / raw)
To: postgresql-general mailing list <pgsql-general@postgresql.org>
From: "Tom Lane" <tgl@sss.pgh.pa.us>
> There are some speed improvements in 8.0 too, though that wasn't the
> main focus of the release cycle. For instance, Lonni Friedman's nearby
> thread reports on a case where 8.0 consistently finds a much better
> query plan for a complex query than prior releases did, because we fixed
> some issues in the GEQO planner module.
Could you give an example or two of the sorts of queries for which
performance is improved under 8.0 compared with 7.4, please Tom?
Thanks
Julian Scarfe
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-27 12:19 Christopher Browne <cbbrowne@acm.org>
parent: Jim C. Nasby <decibel@decibel.org>
2 siblings, 0 replies; 11+ messages in thread
From: Christopher Browne @ 2005-02-27 12:19 UTC (permalink / raw)
To: pgsql-general@postgresql.org
Yes, that certainly ought to work.
If what you're meaning is that you make a replica that sits in
/opt/VERSION8, and then, once the upgrade is complete, rename that to
/opt/MYDATABASE which was where your version 7.4 DB used to be.
We have copied databases from one server to another by copying the
files; making it work was as easy as making sure we ran "pg_ctl -D
$RIGHT_DIRECTORY start" :-).
--
let name="cbbrowne" and tld="cbbrowne.com" in name ^ "@" ^ tld;;
http://cbbrowne.com/info/lisp.html
"I don't know why, but first C programs tend to look a lot worse than
first programs in any other language (maybe except for FORTRAN, but
then I suspect all FORTRAN programs look like `firsts')" -- Olaf Kirch
^ permalink raw reply [nested|flat] 11+ messages in thread
* Re: postgresql 8.0 advantages
@ 2005-02-27 20:27 Tino Wildenhain <tino@wildenhain.de>
parent: Jim C. Nasby <decibel@decibel.org>
2 siblings, 0 replies; 11+ messages in thread
From: Tino Wildenhain @ 2005-02-27 20:27 UTC (permalink / raw)
To: Jim C. Nasby <decibel@decibel.org>; +Cc: Jeff Davis <jdavis-pgsql@empires.org>; schen@graciousstyle.com, PgSQL General List <pgsql-general@postgresql.org>
Hi,
Am Samstag, den 26.02.2005, 15:35 -0600 schrieb Jim C. Nasby:
> On Sat, Feb 26, 2005 at 01:27:55AM -0800, Jeff Davis wrote:
> > On Fri, 2005-02-25 at 09:20 -0800, Si Chen wrote:
> > > Thanks!
> > >
> > > Is there any documentation on how to upgrade to 8.0?
> > >
> > > Is it possible to upgrade from 7.4 to 8.0 while keeping a production
> > > database running "in place"? Or should I install 8.0 in another
> > > directory/machine and then restore the database into it? Are there any
> > > incompatibilities/modifications to databases from the earlier veresion
> > > required?
> > >
> >
> > You might want to check out Slony-I <http://www.slony.info; for the
> > purpose of upgrading. Slony is actually a replication engine, but it can
> > be used to upgrade with little or no downtime. Otherwise, just
> > dump/upgrade/restore like normal.
>
> Has anyone tried moving a database from one location to another on the
> HD? I'd like to use slony to minimize downtime, but I'd also like my
> data to end up in the same place it is right now when I'm done.
I used a straight copy of the filesystem with running database
(over the net in my case) and immediately after that,
stop the db and rsync for the last changes. This took only
10 minutes (compared to 1.5h for the full filesystem copy)
and I could start up the db in new location.
this could work for you too.
Regards
Tino
^ permalink raw reply [nested|flat] 11+ messages in thread
end of thread, other threads:[~2005-02-27 20:27 UTC | newest]
Thread overview: 11+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-02-25 14:41 postgresql 8.0 advantages Si Chen <schen@graciousstyle.com>
2005-02-25 14:53 ` Sean Davis <sdavis2@mail.nih.gov>
2005-02-25 16:15 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-02-25 17:20 ` Si Chen <schen@graciousstyle.com>
2005-02-25 17:20 ` Lonni J Friedman <netllama@gmail.com>
2005-02-26 09:27 ` Jeff Davis <jdavis-pgsql@empires.org>
2005-02-26 21:35 ` Jim C. Nasby <decibel@decibel.org>
2005-02-27 02:12 ` Christopher Browne <cbbrowne@acm.org>
2005-02-27 12:19 ` Christopher Browne <cbbrowne@acm.org>
2005-02-27 20:27 ` Tino Wildenhain <tino@wildenhain.de>
2005-02-27 10:58 ` Julian Scarfe <julian@avbrief.com>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox