[DOCS] PostgreSQL.conf / runtime docs

2004-08-06 Thread Josh Berkus
Folks,

I want to put some serious work into these.   However, I won't have all the 
data I need to update them until we're close to release; I need to do some 
serious performance testing on 8.0beta so that I can have actual numbers to 
recommend.

As we've always accepted doc patches up until a few days before release, this 
shouldn't be a problem, yes?  (Besides, I still need to fix the SGML 
libraries on my laptop ... )

-- 
Josh Berkus
Aglio Database Solutions
San Francisco

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

   http://www.postgresql.org/docs/faqs/FAQ.html


Re: [DOCS] PostgreSQL.conf / runtime docs

2004-08-06 Thread Tom Lane
Josh Berkus <[EMAIL PROTECTED]> writes:
> As we've always accepted doc patches up until a few days before
> release, this shouldn't be a problem, yes?

I'd be really surprised if anyone wants to change that policy.

regards, tom lane

---(end of broadcast)---
TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]


[DOCS] Patch for plpgsql.sgml

2004-08-06 Thread Devrim GUNDUZ
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1


Hi,

As Tom has pointed out today, I've began reading the docs. plpgsql.sgml 
says that PostgreSQL does not support nested transactions. I've removed 
that part and a small diff is attached.

I'll be on 10-days' holiday and I'll try to read the whole docs.

Regards,
- -- 
Devrim GUNDUZ  
devrim~gunduz.org   devrim.gunduz~linux.org.tr 
http://www.tdmsoft.com
http://www.gunduz.org
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBE9Lztl86P3SPfQ4RAtN9AKDjSR6Xlgl3ea2su1pDgOnsd1q27ACeLvT+
aeF83FCl8/3ccbCdauwt6Wg=
=Oks/
-END PGP SIGNATURE-
--- doc/src/sgml/plpgsql.sgml.orig  2004-08-06 12:05:10.0 +0300
+++ doc/src/sgml/plpgsql.sgml   2004-08-06 12:05:47.0 +0300
@@ -450,9 +450,7 @@
  grouping statements in PL/pgSQL with the database commands for
  transaction control.  PL/pgSQL's 
BEGIN/END are only for grouping;
  they do not start or end a transaction.  Functions and trigger procedures
- are always executed within a transaction established by an outer query
- --- they cannot start or commit transactions, since
- PostgreSQL does not have nested transactions.
+ are always executed within a transaction established by an outer query.
 
   
 

---(end of broadcast)---
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])


Re: [DOCS] PostgreSQL.conf / runtime docs

2004-08-06 Thread Bruce Momjian
Tom Lane wrote:
> Josh Berkus <[EMAIL PROTECTED]> writes:
> > As we've always accepted doc patches up until a few days before
> > release, this shouldn't be a problem, yes?
> 
> I'd be really surprised if anyone wants to change that policy.

Agreed.  We take doc improvements anytime!

-- 
  Bruce Momjian|  http://candle.pha.pa.us
  [EMAIL PROTECTED]   |  (610) 359-1001
  +  If your life is a hard drive, |  13 Roberts Road
  +  Christ can be your backup.|  Newtown Square, Pennsylvania 19073

---(end of broadcast)---
TIP 9: the planner will ignore your desire to choose an index scan if your
  joining column's datatypes do not match