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).

version number from the current database, and couldn't find any existing
program to do that.

linda:~$ pg_controldata
Log file id:                          0
Log file segment:                     5
Last modified:                        Wed Feb  7 19:35:47 2001
Database block size:                  8192
Blocks per segment of large relation: 131072
Catalog version number:               200101061
LC_COLLATE:                           en_GB
LC_CTYPE:                             en_GB
Log archive directory:

Oliver Elphick                                Oliver.Elphick@lfix.co.uk

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 ...

update to beta5 ... I think I ran cvs2cl right this time? :)

update to beta5

Eiji Tokuya" <e-tokuya@Mail.Sankyo-Unyu.co.jp>

 Linux/Alpha, Linux/Sparc, MacOS-X.

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.

semantics, a few other small improvements.

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.

markup. ;-)

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.