| Commit message (Collapse) | Author | Age |
... | |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
threadsafe patch from Karl von Randow applied
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
planning to modify them itself. Otherwise we end up with shared RTE
substructure, which breaks inheritance_planner because the rte->inh
flag needs to be independent in each copied subquery. Per bug report
from Chris Piker.
|
|
|
|
|
| |
attr_needed/attr_widths optimization failed to allow for Vars with attno
zero in this case. Per report from Tatsuo Ishii.
|
|
|
|
| |
order. Remove some unnecessary #includes (that duplicate c.h).
|
|
|
|
|
| |
prevents view from showing constraints on domains. This addresses the
other half of Claus Colloseus' bug report.
|
|
|
|
| |
for bit(x), the typmod stores x+4, like for the character types.)
|
|
|
|
|
|
|
|
| |
reduce the number of times TopoSort() has to be executed by trying to
extract multiple dependency loops from each pass, instead of only one.
This saves about another factor of ten on the regression database.
This could be considered as another exercise in grokking Fred Brooks'
maxim: Representation *is* the essence of programming.
|
|
|
|
|
| |
functionality. Per bug report by Alvar Freude:
http://archives.postgresql.org/pgsql-bugs/2003-12/msg00022.php
|
|
|
|
| |
bottleneck in the new pg_dump code.
|
|
|
|
|
|
| |
one (use a priority heap to keep track of items ready to output, instead
of searching the input array each time). This brings the runtime of
pg_dump back to about what it was in 7.4.
|
|
|
|
|
|
|
| |
pg_depend to determine a safe dump order. Defaults and check constraints
can be emitted either as part of a table or domain definition, or
separately if that's needed to break a dependency loop. Lots of old
half-baked code for controlling dump order removed.
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
to certain compile-time options (FUNC_MAX_ARGS, INDEX_MAX_KEYS,
NAMEDATALEN, BLCKSZ, HAVE_INT64_TIMESTAMP). Also added "category",
"short_desc", and "extra_desc" to the pg_settings view. Per recent
discussion here:
http://archives.postgresql.org/pgsql-patches/2003-11/msg00363.php
|
|
|
|
|
|
| |
and hash bucket-size estimation. Issue has been there awhile but is more
critical in 7.4 because it affects varchar columns. Per report from
Greg Stark.
|
| |
|
|
|
|
|
|
| |
transaction has been committed without SPI_finish() being called
first. Per recent discussion here:
http://archives.postgresql.org/pgsql-patches/2003-11/msg00286.php
|
| |
|
| |
|
|
|
|
| |
Andrew Dunstan
|
|
|
|
|
|
|
| |
(again). Please consider this patch for the 7.4.1 branch (if there will
be one) too.
Jason Tishler
|
|
|
|
| |
Neil Conway
|
|
|
|
|
|
|
|
|
|
|
| |
\lo_export LOBOID FILE
\lo_import FILE [COMMENT]
\lo_list
\lo_unlink LOBOID large object operations
Instead of not saying anything about what arguments are required.
Christopher Kings-Lynne
|
|
|
|
| |
Claudio Natoli
|
|
|
|
|
|
| |
\du and a \dg command to psql. It's against 7.4beta5.
Markus Bertheau <twanger@bluetwanger.de>
|
|
|
|
|
|
| |
on 64-bit Solaris. Use a non-system-dependent datatype for UsedShmemSegID,
namely unsigned long (which we were already assuming could hold a shmem
key anyway, cf RecordSharedMemoryInLockFile).
|
|
|
|
|
|
|
| |
comments in the psql code. This doesn't make any functional change, so
feel free to save it for 7.5
Neil Conway
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
definitions use pretty printing.
It does:
* Pretty index predicates
* Pretty rule definitions
* Uppercases PRIMARY KEY and UNIQUE to be consistent with CHECK and
FOREIGN KEY
* View rules are improved to match table rules:
Christopher Kings-Lynne
|
|
|
|
|
|
|
|
| |
proposal for eventually deprecating OIDs on user tables that I posted
earlier to pgsql-hackers. pg_dump now always specifies WITH OIDS or
WITHOUT OIDS when dumping a table. The documentation has been updated.
Neil Conway
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
method control structure, or a table of control structures.
. Use type LOCKMASK where an int is not a counter.
. Get rid of INVALID_TABLEID, use INVALID_LOCKMETHOD instead.
. Use INVALID_LOCKMETHOD instead of (LOCKMETHOD) NULL, because
LOCKMETHOD is not a pointer.
. Define and use macro LockMethodIsValid.
. Rename LOCKMETHOD to LOCKMETHODID.
. Remove global variable LongTermTableId in lmgr.c, because it is
never used.
. Make LockTableId static in lmgr.c, because it is used nowhere else.
Why not remove it and use DEFAULT_LOCKMETHOD?
. Rename the lock method control structure from LOCKMETHODTABLE to
LockMethodData. Introduce a pointer type named LockMethod.
. Remove elog(FATAL) after InitLockTable() call in
CreateSharedMemoryAndSemaphores(), because if something goes wrong,
there is elog(FATAL) in LockMethodTableInit(), and if this doesn't
help, an elog(ERROR) in InitLockTable() is promoted to FATAL.
. Make InitLockTable() void, because its only caller does not use its
return value any more.
. Rename variables in lock.c to avoid statements like
LockMethodTable[NumLockMethods] = lockMethodTable;
lockMethodTable = LockMethodTable[lockmethod];
. Change LOCKMETHODID type to uint16 to fit into struct LOCKTAG.
. Remove static variables BITS_OFF and BITS_ON from lock.c, because
I agree to this doubt:
* XXX is a fetch from a static array really faster than a shift?
. Define and use macros LOCKBIT_ON/OFF.
Manfred Koizar
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to note:
1) arttype is numeric. I thought this was the best way of allowing
arbitarily large factorials, even though factorial(2^63) is a large
number. Happy to change to integers if this is overkill.
2) since we're accepting numeric arguments, the patch tests for floats.
If a numeric is passed with non-zero decimal portion, an error is raised
since (from memory) they are undefined.
Gavin Sherry
|
|
|
|
| |
per gripe from Joe Sunday.
|
|
|
|
|
| |
since there is no need to worry about damaged pages when we are going to
overwrite them anyway from the WAL. Per recent discussion.
|
|
|
|
|
|
| |
while you can actually set them with SET.
This applied patch changes the wording from "Show" to "Set".
|
|
|
|
|
|
| |
octal escape all octets outside the range 0x20 to 0x7e. This fixes
the problem pointed out by Sergey Yatskevich here:
http://archives.postgresql.org/pgsql-bugs/2003-11/msg00140.php
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
standalone backend --- the CVS revision number of postgres.c is not real
useful to anyone.
|