| Commit message (Collapse) | Author | Age |
... | |
|
|
|
|
|
|
|
|
|
|
| |
only if at least N other backends currently have open transactions. This
is not a great deal of intelligence about whether a delay might be
profitable ... but it beats no intelligence at all. Note that the default
COMMIT_DELAY is still zero --- this new code does nothing unless that
setting is changed.
Also, mark ENABLEFSYNC as a system-wide setting. It's no longer safe to
allow that to be set per-backend, since we may be relying on some other
backend's fsync to have synced the WAL log.
|
|
|
|
|
|
| |
does not lead to a one-second delay, but to an immediate EINVAL failure.
This causes CHECKPOINT to crash with s_lock_stuck much too quickly :-(.
Fix by breaking down the requested wait div/mod 1e6.
|
|
|
|
|
| |
proc_exit(1). Unless you think a system-wide restart is an appropriate
response to bogus PGOPTIONS, that is.
|
|
|
|
|
| |
on some platforms, which is not too surprising considering how platform
specific these macros must be).
|
|
|
|
|
| |
right. We should MAXALIGN the individual items because we'll
allocate them individually, not as an array.
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
> Is there one LOCKMETHODCTL for every backend? I thought there was only
> one of them.
>>
>> You're right, that line is erroneous; it should read
>>
>> size += MAX_LOCK_METHODS * MAXALIGN(sizeof(LOCKMETHODCTL));
>>
>> Not a significant error but it should be changed for clarity ...
|
| |
|
| |
|
|
|
|
| |
Eiji Tokuya" <e-tokuya@Mail.Sankyo-Unyu.co.jp>
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
up the comments later.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if it's correct to post here.
It's simple to do the translation, And I've test in 7.0.2 & current CVS,
seems pretty good.
If anyone want this little thing, I'll very happy.
use it is very simple, just gunzip it and copy to
$PGDIR/share/pgaccess/lib/languages/ for current CVS version,
and $PGDIR/pgaccess/lib/languages/ for 7.0*
BTW: I havn't got the tools to translate it to BIG5 encoding, is there
anybody to to it?
He Weiping(Laser Henry)
|
|
|
|
| |
during WAL recovery. Recovery failure is always serious.
|
| |
|
| |
|
|
|
|
|
| |
reported by Matteo Cavalleri.
Great thanks to Tom for his accurate analysis.
|
|
|
|
| |
microseconds < 100000 should be displayed as, eg, 13.000126, not 13.126.
|
| |
|
|
|
|
|
|
|
| |
in Turkish locale. Keywords are now checked under pure ASCII case-folding
rules ('A'-'Z'->'a'-'z' and nothing else). However, once a word is
determined not to be a keyword, it will be case-folded under the current
locale, same as before. See pghackers discussion 20-Feb-01.
|
|
|
|
| |
in multi-byte build.
|
| |
|
| |
|
|
|
|
|
|
| |
be lurking in the install target directory. But don't zap up-to-date
headers (so install-all-headers before regular install will work).
Per suggestion from Larry Rosenman.
|
| |
|
|
|
|
| |
or library directories on the command line.
|
| |
|
|
|
|
| |
so that we don't reject overlength names unnecessarily.
|
| |
|
|
|
|
|
|
| |
use the ANSI varargs style (<stdarg.h>) not the old style. Tatsuo had
reported this change was necessary back in the 7.0 beta cycle (4/13/00)
but for some reason, making the edit never got done.
|
|
|
|
| |
syntax. Fix the RESULT_OID case, which never worked. Add documentation.
|
| |
|
| |
|
|
|
|
| |
the ones specified by SQL.
|
|
|
|
|
|
| |
option of CREATE DATABASE. In pg_regress, create regression database
from template0 to ensure that any installation-local cruft in template1
will not mess up the tests.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
waste of cycles on single-CPU machines, and of dubious utility on multi-CPU
machines too.
Tweak s_lock_stuck so that caller can specify timeout interval, and
increase interval before declaring stuck spinlock for buffer locks and XLOG
locks.
On systems that have fdatasync(), use that rather than fsync() to sync WAL
log writes. Ensure that WAL file is entirely allocated during XLogFileInit.
|
|
|
|
|
|
| |
either wrong or unnecessary in most cases, and on systems where setting
status takes a kernel call, the overhead of setting status three times
per command rather than two is annoying.
|
| |
|
|
|
|
| |
if it returns EINTR.
|
|
|
|
| |
FileWrite, FileSeek.
|
|
|
|
|
| |
to generate unnecessarily stupid code. Tweak macro to describe a series
of store-constant ops, not store/load/store/load/store/load/store.
|
|
|
|
| |
with encoding other than SQL_ASCII. Per recent discussion in pghackers.
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fri Feb 17 15:11:00 GMT 2001 peter@retep.org.uk
- Reduced the object overhead in PreparedStatement by reusing the same
StringBuffer object throughout. Similarly SimpleDateStamp's are alse
reused in a thread save manner.
- Implemented in PreparedStatement: setNull(), setDate/Time/Timestamp
using Calendar, setBlob(), setCharacterStream()
- Clob's are now implemented in ResultSet & PreparedStatement!
- Implemented a lot of DatabaseMetaData & ResultSetMetaData methods.
We have about 18 unimplemented methods left in JDBC2 at the current
time.
|
| |
|