<!--

$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.10 2000/09/29 20:21:33 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/arch-dev.sgml,v 2.11 2000/12/21 22:55:26 petere Exp $

-->

<chapter id="overview">

{\it parsetree} given by the parameter {\tt parsetree}. This is done

by adding a new {\tt AND} node and attaching the old and the new {\it

operator tree} as arguments to it. {\tt AddHavingQual()} has not been

existing untilv6.3.2. It has been created for the {\it having logic}.

existing untilversion 6.3.2. It has been created for the {\it having logic}.

%

\begin{verbatim}

void

This function is similar to the above described function {\tt

AddHavingQual()}. It also adds the {\it operator tree} given by the

parameter {\tt havingQual} but prefixes it by a {\tt NOT} node. {\tt

AddNotHavingQual()} has also not been existing untilv6.3.2 and has been

AddNotHavingQual()} has also not been existing untilversion 6.3.2 and has been

created for the {\it having logic}.

%

\begin{verbatim}

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.10 2000/09/29 20:21:33 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/cvs.sgml,v 1.11 2000/12/21 22:55:26 petere Exp $

CVS code repository

Thomas Lockhart

-->

</para>

<para>

So, to create thev6.4 release

So, to create the6.4 release

I did the following:

<programlisting>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.13 2000/10/20 13:57:10 thomas Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/datetime.sgml,v 2.14 2000/12/21 22:55:27 petere Exp $

Date/time details

-->

Gregorian years 1-99AD may be entered by using 4 digits with leading

zeros (e.g. 0099 is 99AD). Previous versions of

<productname>Postgres</productname> accepted years with three

digits and with single digits, but as ofv7.0 the rules have

digits and with single digits, but as ofversion 7.0 the rules have

been tightened up to reduce the possibility of ambiguity.

</para>

</tip>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.10 2000/09/29 20:21:34 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/history.sgml,v 1.11 2000/12/21 22:55:27 petere Exp $

-->

<sect1 id="history">

<listitem>

<para>

Overall backend code speed has been increased by approximately 20-40%,

and backend start-up time has decreased 80% sincev6.0 was released.

and backend start-up time has decreased 80% sinceversion 6.0 was released.

</para>

</listitem>

</itemizedlist>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.15 2000/10/27 22:28:23 momjian Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/Attic/jdbc.sgml,v 1.16 2000/12/21 22:55:27 petere Exp $

-->

<chapter id="jdbc">

For <productname>Postgres</productname>, you must access large

objects within an SQL transaction. Although this has always been

true in principle, it was not strictly enforced until the

release ofv6.5. You would open a transaction by using the

release ofversion 6.5. You would open a transaction by using the

<function>setAutoCommit()</function> method with an input

parameter of <literal>false</literal>:

<para>

<ulink url="http://www.retep.org.uk">My own web site</ulink>

contains updated information not included in this

document, and also includes precompiled drivers forv6.4, and earlier.

document, and also includes precompiled drivers forversions 6.4 and earlier.

</para>

</sect1>

</chapter>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.13 2000/09/29 20:21:34 petere Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/lobj.sgml,v 1.14 2000/12/21 22:55:27 petere Exp $

-->

<chapter id="largeObjects">

<para>

All large object manipulation <emphasis>must</emphasis> take

place within an SQL transaction. This requirement is strictly

enforced as of Postgresv6.5, though it has been an

enforced as of Postgres6.5, though it has been an

implicit requirement in previous versions, resulting in

misbehavior if ignored.

</para>

<!--

$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.10 2000/05/02 20:01:52 thomas Exp $

$Header: /cvsroot/pgsql/doc/src/sgml/notation.sgml,v 1.11 2000/12/21 22:55:27 petere Exp $

-->

<sect1 id="terminology">

<note>

<para>

At the time of writing (<Productname>Postgres</Productname>v7.0)

At the time of writing (<Productname>Postgres</Productname>7.0)

the notation for

flagging commands is not universally consistant throughout the

documentation set.

<Para>

<ProductName>Postgres</ProductName> uses a message-based protocol for communication between frontends

and backends. The protocol is implemented over <Acronym>TCP/IP</Acronym> and also on Unix sockets.

<ProductName>Postgres</ProductName>v6.3 introduced version numbers into the protocol.

<ProductName>Postgres</ProductName>6.3 introduced version numbers into the protocol.

This was done in such

a way as to still allow connections from earlier versions of frontends, but

this document does not cover the protocol used by those earlier versions.

</para>

<Para>

This document describes version 2.0 of the protocol, implemented in

<ProductName>Postgres</ProductName>v6.4 and later.

<ProductName>Postgres</ProductName>6.4 and later.

</para>

<Para>