pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Eric Mueller <eric@themepark.com>
To: 'PostgreSQL general mailing list' <pgsql-general@postgresql.org>
Subject: RE: RE: Re: MySQL and PostgreSQL speed compare
Date: Tue, 2 Jan 2001 16:20:53 -0800
Message-ID: <000f01c0751b$09441f00$d534a9ac@vaio> (raw)
In-Reply-To: <20010102175326.A48258@over-yonder.net>

I'm happy to contribute once I feel like I've got something to offer, which
I won't know until I have the lay of the land, and that's the problem. As a
long-time coder picking up postgresql for the first time, I'm baffled by
what seems to be a lack of detailed documentation for something so
fundamental as the built-in functions. Do the docs for the functions even
exist? Are they in the dist but not published on the web site? Zen-like
riddles and causes-in-need-of-aid aside, any hints to the answer for such a
basic question would help me get started with what seems like a very
powerful tool.

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org]On Behalf Of GH
Sent: Tuesday, January 02, 2001 3:53 PM
To: Eric Mueller
Cc: 'PostgreSQL general mailing list'
Subject: Re: RE: Re: MySQL and PostgreSQL speed compare

On Tue, Jan 02, 2001 at 02:47:05PM -0800, some SMTP stream spewed forth:
> ...another advantage I've seen is the documentation! MySQL has its
functions
> clearly documented on the mysql.com site; I not able to find detailed docs
> for the pgsql functions anywhere on the postgresql site.

I ask you the same question I ask myself in such situations:
How much documentation have I written?
How much have I aided the Cause?

gh

>
> -----Original Message-----
> From: pgsql-general-owner@postgresql.org
> [mailto:pgsql-general-owner@postgresql.org]On Behalf Of Bruce Momjian
> Sent: Tuesday, January 02, 2001 1:08 PM
> To: kientzle@acm.org
> Cc: PostgreSQL general mailing list
> Subject: Re: Re: MySQL and PostgreSQL speed compare
>
> > One big advantage of MySQL over PostgreSQL
> > right now is ease of upgrading.  Upgrading
> > MySQL just requires shutting down the old
> > one and starting the new; PostgreSQL requires
> > a more involved process to migrate all of
> > your data.  (Of course, upgrading your DB
> > is never a simple matter, but at least
> > MySQL tries to make it less painful.)
>
> Yes, that is a good point.  We are clearly fixing/improving the storage
> system, while MySQL has been able to keep the same one for many years.
>
> --
>   Bruce Momjian                        |  http://candle.pha.pa.us
>   pgman@candle.pha.pa.us               |  (610) 853-3000
>   +  If your life is a hard drive,     |  830 Blythe Avenue
>   +  Christ can be your backup.        |  Drexel Hill, Pennsylvania 19026
>





view thread (22+ messages)  latest in thread

Message-ID: <000f01c0751b$09441f00$d534a9ac@vaio>
Permalink:  ../000f01c0751b$09441f00$d534a9ac@vaio/
Also on:    postgresql.org/message-id/000f01c0751b$09441f00$d534a9ac@vaio

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: eric@themepark.com, pgsql-general@postgresql.org
  Subject: RE: RE: Re: MySQL and PostgreSQL speed compare
  In-Reply-To: <000f01c0751b$09441f00$d534a9ac@vaio>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

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