Mikheev, Vadim wrote:
> > I have verified that killing the postmaster after a few nextval's
> > leaves things in a bad state after restart.
> >
> > I think I see the problem: in nextval(), the sequence data written to
> > the WAL log is different from that written to the data page. Isn't
> > tha
[EMAIL PROTECTED] writes:
> I propose to make the documentation more concise in this point and to
> add a macro like:
> #define palloc_tx(sz) MemoryContextAlloc(TopTransactionContext, (sz))
I don't think it's a good idea to encourage people to allocate in
TopTransactionContext as a substitute f
Holger Krug ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Misleading documentation of `palloc'
Long Description
In section 12.5.6 "Writing Code" of the "PostgreSQL 7.2 Programmer's
Guide" the following is said:
"When alloca
