pgsql y2k bug?

From: Ed Loehr <eloehr(at)austin(dot)rr(dot)com>
To: pghackers <pgsql-hackers(at)postgresql(dot)org>
Subject: pgsql y2k bug?
Date: 2000-01-02 00:28:20
Message-ID: 386E9BA4.3E9C1651@austin.rr.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

With pg 6.5.2, I just noticed this timestamped vacuum output in
my log file...

1000101.18:14:18.555 [6514] DEBUG: --Relation
ui_option_choice--
1000101.18:14:18.555 [6514] DEBUG: Pages 1: Changed 0, Reapped
0, Empty 0, New 0; Tup 5: Vac 0, Keep/VTL 0/0, Crash 0, UnUsed 0,
MinLen 68, MaxLen 100; Re-using: Free/Avail. Space 0/0;
EndEmpty/Avail. Pages 0/0. Elapsed 0/0 sec.
1000101.18:14:18.558 [6514] DEBUG: Index ui_option_choice_pkey:
Pages 2; Tuples 5. Elapsed 0/0 sec.
1000101.18:14:18.558 [6514] DEBUG: Index
ui_option_choice_id_key: Pages 2; Tuples 5. Elapsed 0/0 sec.
1000101.18:14:18.570 [6514] DEBUG: --Relation
ui_default_preference--

Notice the Jan 1, 100 A.D. timestamp...

% date
Sat Jan 1 18:24:20 CST 2000

AFAICT, this is limited to the logging mechanism (datetime output
appears fine).

Cheers,
Ed Loehr

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2000-01-02 01:42:57 Re: [HACKERS] pgsql y2k bug?
Previous Message Ed Loehr 2000-01-01 19:05:18 Re: [HACKERS] dubious improvement in new psql