| Age | Commit message (Collapse) | Author |
|---|
|
PgDatabase::DisplayTuples and PgDatabase::PrintTuples. This is incorrect
according to strict interpretation of the C++ spec, and some compilers
will reject it. Also silence g++ warning about unused parameter.
|
|
The patch will avoid to add .exe suffix to the pg_encoding
binary.
|
|
the gettimeofday doesn't compile under Linux with glibc2 because
the DST_NONE constant is no more defined. It seems that this code
(written by me) has always be wrong but for some reason working.
From: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
the default target is 'install' instead of 'all'. So if you do a
make without target you actually do a make install, which is not
what one normally expects from a standard makefile.
From: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
the ecpg Makefiles use a variable DESTDIR which is never defined
except by debian/rules makefile, in which case the ecpg makefiles
expand wrong pathnames. If we want to support a DESTDIR root it
must be done consistently in all the makefiles, not just in ecpg.
From: Massimo Dal Zotto <dz@cs.unitn.it>
|
|
they were confusing because the large object tables themselves are not
shown. (Besides, if you've got hundreds or thousands of large objects,
you really don't want to see 'em at all.)
Also, suppress all indexes from the \z ACL listing, since indexes have
no meaningful protection information.
|
|
given number of backends (-N), per recent discussion in pghackers list.
|
|
|
|
Get rid of it to make customization of NAMEDATALEN easier.
|
|
|
|
|
|
|
|
in the same transaction that created it.
|
|
SET TRANSACTION ISOLATION LEVEL READ COMMITTED;
^^^^ required
Also note that SET TRANSACTION ISOLATION LEVEL change
isolevel for _current_ transaction, in accordance with
standard, not for session (ALTER SESSION is used in Oracle,
but it's not implemented currently).
And I would don't mention SET XACTISOLEVEL TO ...
form at all.
Please update set.sgml - I failed to understand all these
SET TIME ZONE { '<REPLACEABLE CLASS="PARAMETER">
now.
for Vadim
|
|
should be described like SET TIME ZONE: TO is not allowed, as well
as DEFAULT option. There are only two forms:
for Vadim.
|
|
|
|
|
|
|
|
|
|
|
|
in CommitTransaction().
2. Changes in GetSnapshotData().
|
|
vc_scanheap().
|
|
transactions will not assume that MyProc transaction was committed
before snapshot calculations. With old MyProc->xid assignment
(in xact.c:StartTransaction()) there was ability to see the same
row twice (I used gdb for this)!...
2. Assignments of InvalidTransactionId to MyProc->xid and MyProc->xmin
are moved from xact.c:CommitTransaction() to
xact.c:RecordTransactionCommit() - this invalidation must be done
before releasing transaction locks or bad (too high) XmaxRecent value
might be used by vacuum ("ERROR: Child itemid marked as unused"
reported by "Hiroshi Inoue" <Inoue@tpf.co.jp>; once again, gdb
allowed me reproduce this error).
|
|
because it ignored the LOs themselves but failed to ignore the indexes
on the LOs. How long has this been broken??
|
|
all the expected keys (it was returning uninitialized memory).
|
|
libpq ...
|
|
Jan
|
|
198.68.123.0/27 the same when indexing them.
D'Arcy
|
|
{
Oid relId;
Oid dbId;
union
{
BlockNumber blkno;
TransactionId xid;
} objId;
>
> Added:
> /*
> * offnum should be part of objId.tupleId above, but would increase
> * sizeof(LOCKTAG) and so moved here; currently used by userlocks only.
> */
> OffsetNumber offnum;
uint16 lockmethod; /* needed by userlocks */
} LOCKTAG;
gmake clean required...
User locks are ready for 6.5 release...
|
|
Vince.
|
|
later.
Vince.
|
|
all fields that should be set). Add a MoveToFront primitive to speed up
one of the hotspots in SearchSysCache.
|
|
memory context at transaction commit or abort.
|
|
in an index doesn't have a restriction selectivity estimator.
|
|
|
|
right circumstances it would leave old and new bucket headers pointing to
the same list of records.
|
|
|
|
(no sense to hold it) or we'll be out of lock entries.
Great thanks to Hiroshi Inoue.
|
|
(Curious that gcc doesn't complain about this code...).
|
|
is poor coding style. I agree.
|
|
file headers, to conform to established Postgres coding style and avoid
warnings from gcc.
|
|
after checking for presence of C++ compiler. Odd we hadn't seen any
reports of problems before...
|
|
when used with egcs --- now it does.
|
|
2. Get rid of locking when updating statistics in vacuum.
3. Use QuerySnapshot in COPY TO and call SetQuerySnashot
in main tcop loop before FETCH and COPY TO.
|
|
|
|
|
|
few percent speedup in INSERT...
|
|
redundant) SearchSysCache searches per table column in an INSERT, which
accounted for a good percentage of the CPU time for INSERT ... VALUES().
Now it only does two searches in the typical case.
|
|
cache access routines.
|
|
through MAXBACKENDS array entries used to be fine when MAXBACKENDS = 64.
It's not so cool with MAXBACKENDS = 1024 (or more!), especially not in a
frequently-used routine like SIDelExpiredDataEntries. Repair by making
procState array size be the soft MaxBackends limit rather than the hard
limit, and by converting SIGetProcStateLimit() to a macro.
|
