| Commit message (Collapse) | Author | Age |
... | |
| |
|
|
|
|
|
|
| |
VFD entries. On platforms where dereferencing a null pointer doesn't
lead to coredump, it's possible that this omission could have led to
unpleasant behavior like deleting the wrong file.
|
|
|
|
| |
include O_CREAT.
|
|
|
|
|
|
| |
physical file has disappeared. There is no really good reason why
relcache should be opening the underlying file at all, AFAICS.
In any case we needn't raise a hard error here.
|
| |
|
|
|
|
|
|
| |
with different default values, unless the child table redeclares the
column with an explicit default. This was judged to be the approach
least likely to cause unpleasant surprises.
|
| |
|
| |
|
|
|
|
| |
now on VAX NetBSD. Hence, remove #ifdef'd disable tests.
|
|
|
|
| |
case of LIMIT in a sub-select.
|
|
|
|
|
|
| |
in CREATE TABLE, but give a warning notice. Clean up inconsistent
handling of defaults and NOT NULL flags from multiply-inherited columns.
Per pghackers discussion 28-Mar through 30-Mar.
|
| |
|
|
|
|
|
|
|
| |
inheritance query: make duplicate copies of subplans in adjust_inherited_attrs.
When we redesign querytrees we really gotta do something about this
issue of whether querytrees are read-only and can share substructure
or not.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
more recent versions of the IBM C++ compiler (now called VisualAge C++).
The C++ part was previously broken (g++ and xlC), thus this is zero risk.
Only AIX specific parts are touched (1 Makefile.shlib line (link with $(COMPILER
) instead
of $(CC) and one shell script line (parameter -C to nm to not demangle C++ symbo
ls for
.exp file)).
I thus ask you to please apply this patch before release.
With or without this patch RC1 on AIX 4.3.2 RS6000 passes "gmake check" for both
the native
compiler vac.C 5.0.1 and gcc 2.95.2 :-)
Andreas
|
| |
|
| |
|
|
|
|
|
|
| |
account.
This connection has been terminated by the administrator.
|
| |
|
|
|
|
| |
be aligned on a word boundary. Per report from Steve Nicolai.
|
|
|
|
|
|
| |
accepts nnnLL syntax for long long constants. If so, decorate the CRC64
constants with LL to avoid warnings and/or erroneous results from certain
non-standards-compliant compilers.
|
|
|
|
| |
can be compiled with asserts enabled on Windoze.
|
| |
|
|
|
|
|
|
|
|
|
| |
on Alpha (because parser mistakenly assumes that a nonoverflow result
from strtol means the value will fit into int4). A scan for other uses
of strtol and strtoul found a couple other places with the same mistake;
fix them too. The changes are all conditional on HAVE_LONG_INT_64 to
avoid complaints from compilers that think x != x is a silly test
(cf. pg_atoi).
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
*before* acquiring shlock on buffer context. This way we should be
protected against conflicts with FlushRelationBuffers.
(Seems we never do excl lock and then StartBufferIO for the same
buffer, so there should be no deadlock here, - but we'd better
check this very soon).
|
|
|
|
| |
Tom Lane.
|
|
|
|
|
| |
it's easier to tell whether a bug report is talking about progressive
memory exhaustion or a wacko requested chunk size.
|
|
|
|
| |
per gripe from Josh Berkus.
|
|
|
|
|
| |
NEXTXID isn't really necessary, per previous discussion in pghackers,
but I mulishy insisted we should put it in anyway. Mea culpa.
|
|
|
|
| |
space in front of it. Improve comments a little.
|
|
|
|
| |
I'm betting the QNX4 port does not either ...
|
|
|
|
| |
work in BeOS port.
|
|
|
|
| |
slow backend, if we update unconditionally as the code did before).
|
|
|
|
|
| |
the new log file with zeroes, only while renaming it into place. This should
prevent problems with 'stuck spinlock' errors under heavy load.
|
|
|
|
|
|
|
|
| |
O_SYNC, or O_DSYNC (as available on a given platform). Add GUC parameter
to control sync method.
Also, add defense to XLogWrite to prevent it from going nuts if passed
a target write position that's past the end of the buffers so far filled
by XLogInsert.
|
|
|
|
| |
to a join or subselect alias ... cf. Oliver Elphick's complaint 13-Mar.
|
|
|
|
| |
is still a memory leak, but a little less bad than it was.
|
|
|
|
|
|
| |
I'm not sure that it's really necessary to save insert events when there
are only after update or delete triggers, but certainly it's wrong for
COPY to behave differently from an INSERT query.
|
| |
|
|
|
|
|
| |
(per recent discussion with Tatsuo). Hopefully the compilers with
that old bug are all long gone.
|
|
|
|
| |
Change the administrator to 'an' administrator.
|
|
|
|
| |
Just try again later.
|
| |
|
|
|
|
| |
This connection has been terminated by the administrator
|
| |
|
|
|
|
|
|
|
|
|
| |
detect case that next page in log came from an older run than the prior
page. This avoids the necessity to re-zero the log after recovery from
a crash, which is good because we need not risk destroying valuable log
information.
This forces another initdb since yesterday :-(. Need to get that log
reset utility done...
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Store two past checkpoint locations, not just one, in pg_control.
On startup, we fall back to the older checkpoint if the newer one
is unreadable. Also, a physical copy of the newest checkpoint record
is kept in pg_control for possible use in disaster recovery (ie,
complete loss of pg_xlog). Also add a version number for pg_control
itself. Remove archdir from pg_control; it ought to be a GUC
parameter, not a special case (not that it's implemented yet anyway).
* Suppress successive checkpoint records when nothing has been entered
in the WAL log since the last one. This is not so much to avoid I/O
as to make it actually useful to keep track of the last two
checkpoints. If the things are right next to each other then there's
not a lot of redundancy gained...
* Change CRC scheme to a true 64-bit CRC, not a pair of 32-bit CRCs
on alternate bytes. Polynomial borrowed from ECMA DLT1 standard.
* Fix XLOG record length handling so that it will work at BLCKSZ = 32k.
* Change XID allocation to work more like OID allocation. (This is of
dubious necessity, but I think it's a good idea anyway.)
* Fix a number of minor bugs, such as off-by-one logic for XLOG file
wraparound at the 4 gig mark.
* Add documentation and clean up some coding infelicities; move file
format declarations out to include files where planned contrib
utilities can get at them.
* Checkpoint will now occur every CHECKPOINT_SEGMENTS log segments or
every CHECKPOINT_TIMEOUT seconds, whichever comes first. It is also
possible to force a checkpoint by sending SIGUSR1 to the postmaster
(undocumented feature...)
* Defend against kill -9 postmaster by storing shmem block's key and ID
in postmaster.pid lockfile, and checking at startup to ensure that no
processes are still connected to old shmem block (if it still exists).
* Switch backends to accept SIGQUIT rather than SIGUSR1 for emergency
stop, for symmetry with postmaster and xlog utilities. Clean up signal
handling in bootstrap.c so that xlog utilities launched by postmaster
will react to signals better.
* Standalone bootstrap now grabs lockfile in target directory, as added
insurance against running it in parallel with live postmaster.
|
|
|
|
|
|
| |
tuples inserted/deleted/updated in a single transaction. On my machine,
this reduced the time to delete 80000 tuples in a foreign-key-referencing
table from ~15min to ~8sec.
|