cache.  I found if I manually added a line to flush the whole relation
cache, the assert error disappeared.  Looking through the code, I found
that the relation cache is flushed at the end of each query if the
reference count is zero for the relation.  However, printf's showed that
the rd_relcnt(reference count) for the accessed query was not returning
to zero after each query.

It turns out the parser was doing a heap_ropen in parser/analyze.c to
get information about the table's columns, but was not doing a
heap_close.

This was causing the query after the ALTER TABLE ADD to see the old
table structure, and the executor's assert was reporting the problem.

used in test drivers.

correct way to do this.  Theoretically you could have a NULL
pointer that isn't represented internally as all 0 bits.  This
guarantees that it convert correctly.

Submitted by: darcy@druid.com (D'Arcy J.M. Cain)

use of long term cooperative locks managed by the user applications.

Submitted by: Massimo Dal Zotto <dz@cs.unitn.it>

works again...

No more scrolling off the screen.

	NAMEDATALEN
	OIDDATALEN
	EUROPEAN_DATES
	HBA
	DEADLOCK_TIMEOUT
	OPENLINK_PATCHES
	NULL_PATCH
	ARRAY_PATCH

Attempting to document and centralize as many of the "defines" as possible...
kinda useless to have defines if nobody knows they exist, eh?

function so I am going to assume that it is such a good idea that no
one sees any point in discussing it.  :-)  I have made two changes -
I have merged this into pgtclCmds.c and I have taken out any code for
updating tuples after the loop body runs.  See comments for discussion
of this.

I have also fixed up the error checking stuff so that break, continue
and syntax errors have the expected result.

Submitted by: D'Arcy Cain

Submitted by: D'Arcy Cain

Submitted by: D'Arcy Cain