Re: [pgsql-www] [DOCS] Typo in README.dist-split

2005-10-16 Thread Dave Page
Done. -Original Message- From: [EMAIL PROTECTED] on behalf of Bruce Momjian Sent: Thu 10/13/2005 10:08 PM To: Alvaro Herrera Cc: pgsql-docs@postgresql.org; [EMAIL PROTECTED]; Marc G. Fournier Subject: Re: [pgsql-www] [DOCS] Typo in README.dist-split For clarity, the last line should be

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Tom Lane
Volkan YAZICI <[EMAIL PROTECTED]> writes: > Revision 1.269: Wed Mar 24 03:44:59 2004 UTC by momjian > Branches: MAIN > ] Add thread locking to SSL and Kerberos connections. > ] > ] I have removed the docs mentioning that SSL and Kerberos are not > ] thread-safe. > ] > ] Manfred Spraul I note that

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Volkan YAZICI
Revision 1.269: Wed Mar 24 03:44:59 2004 UTC by momjian Branches: MAIN ] Add thread locking to SSL and Kerberos connections. ] ] I have removed the docs mentioning that SSL and Kerberos are not ] thread-safe. ] ] Manfred Spraul Diff to previous 1.268: http://developer.postgresql.org/cvsweb.cgi/pgs

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > Tom Lane wrote: > >> Really? Do we intend applications to call it? > > > Uh, well, we never call it ourselves, so if we don't expect other > > applications to call it, why is it there? > > If it's intended for apps to call, how was the patch initially

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Tom Lane
Bruce Momjian writes: > Tom Lane wrote: >> Really? Do we intend applications to call it? > Uh, well, we never call it ourselves, so if we don't expect other > applications to call it, why is it there? If it's intended for apps to call, how was the patch initially accepted with no documentation?

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Bruce Momjian
Tom Lane wrote: > Bruce Momjian writes: > > Volkan YAZICI wrote: > >> Will PQregisterThreadLock() - which is defined globally in > >> src/interfaces/libpq/fe-connect.c - be documented? > > > Yes, it should be documented. > > Really? Do we intend applications to call it? Uh, well, we never call

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Tom Lane
Bruce Momjian writes: > Volkan YAZICI wrote: >> Will PQregisterThreadLock() - which is defined globally in >> src/interfaces/libpq/fe-connect.c - be documented? > Yes, it should be documented. Really? Do we intend applications to call it? regards, tom lane

Re: [DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Bruce Momjian
Volkan YAZICI wrote: > Will PQregisterThreadLock() - which is defined globally in > src/interfaces/libpq/fe-connect.c - be documented? Yes, it should be documented. -- Bruce Momjian| http://candle.pha.pa.us pgman@candle.pha.pa.us | (610) 359-1001 +

[DOCS] Will PQregisterThreadLock() be documented?

2005-10-16 Thread Volkan YAZICI
Will PQregisterThreadLock() - which is defined globally in src/interfaces/libpq/fe-connect.c - be documented? ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster