inconsistent coding practices for handling Index values and booleans,
too.

before calling RelationInvalidateHeapTuple(), which is bad because the
latter needs to look at the tuple data, which is in the shared disk
buffer.  If another backend manages to recycle the buffer while this
is going on, we will compute the wrong hashindex for the tuple or
maybe even crash outright.  Must hold buffer refcount until afterwards.
(This bug is not in 7.0.*; seems to be have introduced during WAL changes.)

that leftover cancel/die requests cannot interfere with exit activities.

of 6 Jan 2001 21:55.

tag configure as beta2 ..

and burn.  Just for added luck, change reading of CONST nodes so that
we do not need to consult pg_type rows while reading them; this means
that no database access occurs during stringToNode.  This requires
changing the order in which const-node fields are written, which means
an initdb is forced.

Disallow cases like adding constraints to sequences :-(, and eliminate
now-unnecessary search of pg_rewrite to decide if a relation is a view.

error, so as to provide a starting point for debugging.

in per-entry sub-memory-context, where they were supposed to go, rather
than in CacheMemoryContext where the code was putting them.  Must've
suffered a severe brain fade when I wrote this :-(

noise.

I threw in spell check run over the whole file.

appendix with comprehensive list of key words.

no longer the case).  Add AND and TRAILING to ColLabel.  All key words
except AS are now at least ColLabel's.

what's actually implemented.

sequences. This is done by disabling multi-byte awareness when it's
not necessary. This is kind of a workaround, not a perfect solution.
However, there is no ideal way to parse broken multi-byte character
sequences. So I guess this is the best way what we could do right
now...

so that transactional control could guarantee the consistency.

could ever have worked...)

deallocated memory later on.

they don't themselves flush any cache entries, only add to to-do lists
that will be processed later.

and revert documentation to describe the existing INHERITS clause
instead, per recent discussion in pghackers.  Also fix implementation
of SQL_inheritance SET variable: it is not cool to look at this var
during the initial parsing phase, only during parse_analyze().  See
recent bug report concerning misinterpretation of date constants just
after a SET TIMEZONE command.  gram.y really has to be an invariant
transformation of the query string to a raw parsetree; anything that
can vary with time must be done during parse analysis.

table, per pghackers discussion around 22-Dec-00.

amounts to checking for -ledit instead of -lreadline.)

used before ...

(and most other places where it needed to output a string literal, too,
except for data INSERT statements).  Per bug report from Easter, 12/1/00.

from sergiop@sinectis.com.ar.

of early December 2000.  COPY BINARY is now TOAST-safe.

to it.  Bad dog.

Previous result did not have correct month boundaries so anything near edge
 cases was suspect (e.g. April was in Q1 and July, August were lumped into
 Q2).
Thanks to Denis Osadchy <osadchy@turbo.nsk.su> for the report.