"Katsuhiko Okano" <[EMAIL PROTECTED]> writes:
> Transaction ID can be specified when recovering using a PITR feature.
> For example, in recovery.conf,
>
> recovery_target_xid = '1100842'
>
The documentation already points out that this feature is currently
useless due to the lack
The following bug has been logged online:
Bug reference: 3401
Logged by: Katsuhiko Okano
Email address: [EMAIL PROTECTED]
PostgreSQL version: Head(20070607)
Operating system: Fedora Core release 5 (Bordeaux)
Description:PITR does not work in the case of recovery_targe
On Thu, Jun 21, 2007 at 06:01:03PM +0900, hyukjoo wrote:
> Each Server installed same OS(CentOS4.3), same kernel(2.6.9-42.0.10.ELsmp),
> same antispam package and use same NFS disks.
> Yes, it's redundant.
> There's no problem of PostgreSQL V8.1 running on HP ML370. But DL380 occur
> System Hang.
+
EBIZ사업본부/ e솔루션개발팀
문혁주 대리 (Hyukjoo Moon)
Tel. 02) 538-9360(EXT none) Fax. 02) 538-9369
C.P 010-3182-2563
e-mail : [EMAIL PROTECTED]
http://www.mobigen.com
-Original Message-
From: hyukjoo [mailto:[EMAIL PROTECTED]
Sent: Thursday,
hyukjoo wrote:
We use PostgreSQL V8.1 for logging spam mail in our antispam solution
CREDISHIELD.
Few month ago, one of CREDISHIELD server Hang occured
include 2 times, 2~3weeks interval.
(The machine is HP DL380G5)
I changed server H/W(DL380G5 -> ML370)3~4 weeks ago,
and now it shows normal sta
The following bug has been logged online:
Bug reference: 3400
Logged by: hyukjoo
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.1
Operating system: CentOS 4.3 kernel: 2.6.9-42.0.10.ELsm
Description:System Hang occur
Details:
Dear sirs.
We use PostgreSQL V8
