Re: Redhat 7.3 time manipulation bug

From: Manuel Sugawara <masm(at)fciencias(dot)unam(dot)mx>
To: Ulrich Drepper <drepper(at)redhat(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Lamar Owen <lamar(dot)owen(at)wgcr(dot)org>, Thomas Lockhart <lockhart(at)fourpalms(dot)org>, Trond Eivind Glomsrød <teg(at)redhat(dot)com>, Hannu Krosing <hannu(at)tm(dot)ee>, PostgreSQL Hackers List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Redhat 7.3 time manipulation bug
Date: 2002-05-22 19:09:18
Message-ID: m3adqshue9.fsf@conexa.fciencias.unam.mx
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

This thread is getting pretty annoying rather than constructive. By
the mean time I can see the users of many db's running under linux
loudly complaining.

As a user of both products (glibc and postgres), I would like to see a
good compromise in both sides. For instance: postgreSQL will implement
it's own time engine in one or to releases (In a few months I can do
it if no one else volunteers) and glibc will revert this change for
one or two releases (I can do it right now). That way everyone will be
happy; particularly me and many others using glibc and postgres.

Regards,
Manuel.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Neil Conway 2002-05-22 19:11:56 ksqo?
Previous Message Lamar Owen 2002-05-22 18:58:38 Re: Redhat 7.3 time manipulation bug