[DOCS] Use of "token" vs "lexeme" in text search documentation

2007-10-15 Thread Tom Lane
The current documentation seems a bit inconsistent in its use of the
terms "token" and "lexeme".  The majority of the text seems to use
"lexeme" exclusively, which is inconsistent with the fact that the
term "token" is exposed by ts_token_type() and friends.  But there
are a few places that seem to use "lexeme" to mean something returned
by a dictionary.

I was considering trying to adopt these conventions:

* What a parser returns is a "token".

* When a dictionary recognizes a token, what it returns is a "lexeme".

This would make the phrase "normalized lexeme" redundant, since we
don't call it a lexeme at all unless it's been normalized.

Comments?

regards, tom lane

---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate


[DOCS] Slony for upgrades

2007-10-15 Thread Bruce Momjian
Seems we didn't have any mention of Slony for upgrades in the migration
section, so I added it:

  
   It is also possible to use Slony to create a slave
   server with the updated version of PostgreSQL.  The
   slave can be on the same computer or a different computer.  Once it
   has synced up with the master server (running the older version of
   PostgreSQL), you can switch masters and make the slave
   the master and shut down the older database instance.  Such a
   switch-over results in only several minutes of downtime for an upgrade.
  

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>http://momjian.us
  EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 7: You can help support the PostgreSQL project by donating at

http://www.postgresql.org/about/donate


[DOCS] correct reference external-projects.sgml

2007-10-15 Thread Hiroshi Saito

Hi.

Please check it.
Thanks!

Regards,
Hiroshi Saito

external-projects_patch
Description: Binary data

---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?

   http://www.postgresql.org/docs/faq


Re: [DOCS] Slony for upgrades

2007-10-15 Thread Jeff Frost

On Mon, 15 Oct 2007, Bruce Momjian wrote:


Seems we didn't have any mention of Slony for upgrades in the migration
section, so I added it:

 
  It is also possible to use Slony to create a slave
  server with the updated version of PostgreSQL.  The
  slave can be on the same computer or a different computer.  Once it
  has synced up with the master server (running the older version of
  PostgreSQL), you can switch masters and make the slave
  the master and shut down the older database instance.  Such a
  switch-over results in only several minutes of downtime for an upgrade.
 


Bruce, do you think we should say several minutes of downtime?  It's been my 
experience that the downtime is usually measurable in seconds.  I don't think 
I've ever had a switchover take more than 1 minute.


Excellent catch and good work by the way!

--
Jeff Frost, Owner   <[EMAIL PROTECTED]>
Frost Consulting, LLC   http://www.frostconsultingllc.com/
Phone: 650-780-7908 FAX: 650-649-1954

---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
  subscribe-nomail command to [EMAIL PROTECTED] so that your
  message can get through to the mailing list cleanly


Re: [DOCS] Slony for upgrades

2007-10-15 Thread Bruce Momjian
Jeff Frost wrote:
> On Mon, 15 Oct 2007, Bruce Momjian wrote:
> 
> > Seems we didn't have any mention of Slony for upgrades in the migration
> > section, so I added it:
> >
> >  
> >   It is also possible to use Slony to create a slave
> >   server with the updated version of PostgreSQL.  The
> >   slave can be on the same computer or a different computer.  Once it
> >   has synced up with the master server (running the older version of
> >   PostgreSQL), you can switch masters and make the slave
> >   the master and shut down the older database instance.  Such a
> >   switch-over results in only several minutes of downtime for an upgrade.
> >  
> 
> Bruce, do you think we should say several minutes of downtime?  It's been my 
> experience that the downtime is usually measurable in seconds.  I don't think 
> I've ever had a switchover take more than 1 minute.
> 
> Excellent catch and good work by the way!

Thanks, changed to seconds.  I thought someone told me <5 minutes a
while ago but I might have been mistaken.

-- 
  Bruce Momjian  <[EMAIL PROTECTED]>http://momjian.us
  EnterpriseDB http://postgres.enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +

---(end of broadcast)---
TIP 2: Don't 'kill -9' the postmaster