Patch applied. Thanks.
---------------------------------------------------------------------------
Philip Yarra wrote:
> Hi, this doco patch is a quick one to add explicit mention of the need for the
> AT clause in threaded ECPG applications. Does this sound okay?
>
> Bruce, yes, I do intend to contribute more than this, but at least this will
> stop some confusion in the meantime.
>
> Regards, Philip Yarra.
>
>
> Index: ecpg.sgml
> ===================================================================
> RCS file: /projects/cvsroot/pgsql-server/doc/src/sgml/ecpg.sgml,v
> retrieving revision 1.54
> diff -c -r1.54 ecpg.sgml
> *** ecpg.sgml 12 Nov 2003 22:47:47 -0000 1.54
> --- ecpg.sgml 18 Nov 2003 23:20:51 -0000
> ***************
> *** 353,358 ****
> --- 353,365 ----
> </programlisting>
> This option is particularly suitable if the application needs to
> use several connections in mixed order.
> + </para>
> +
> + <para>
> + If your application uses multiple threads of execution, they cannot
> share a
> + connection concurrently. You must either explicitly control access to
> the connection
> + (using mutexes) or use a connection for each thread. If each thread
> uses its own connection,
> + you will need to use the AT clause to specify which connection the
> thread will use.
> </para>
>
> <para>
>
> -------------------------------------------------------
>
>
> ---------------------------(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
>
-- Bruce Momjian | http://candle.pha.pa.us pgman@candle.pha.pa.us | (610)
359-1001+ If your life is a hard drive, | 13 Roberts Road + Christ can be your backup. | Newtown Square,
Pennsylvania19073