From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, Christoph Berg <myon(at)debian(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
Date: | 2019-06-20 16:14:00 |
Message-ID: | 20190620161400.6wtuybv64ihnfy6d@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Hi,
On 2019-06-20 12:02:30 -0400, Robert Haas wrote:
> On Thu, Jun 20, 2019 at 8:52 AM Stephen Frost <sfrost(at)snowman(dot)net> wrote:
> > I don't want to come across as implying that I'm saying what was done
> > was 'fine', or that we shouldn't be having this conversation, I'm just
> > trying to figure out how we can frame it in a way that we learn from it
> > and work to improve on it for the future, should something like this
> > happen again.
>
> I agree that it's a difficult situation. I do kind of wonder whether
> we were altogether overreacting. If we had shipped it as it was,
> what's the worst thing that would have happened?
I think it's not good, but also nothing particularly bad came out of
it. I don't think we should try to set up procedures for future
occurances, and rather work/plan on that not happening very often.
Greetings,
Andres Freund
From | Date | Subject | |
---|---|---|---|
Next Message | Stephen Frost | 2019-06-20 17:26:58 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
Previous Message | Robert Haas | 2019-06-20 16:02:30 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2019-06-20 16:25:56 | Re: POC: Cleaning up orphaned files using undo logs |
Previous Message | Andres Freund | 2019-06-20 16:05:19 | Re: check_recovery_target_lsn() does a PG_CATCH without a throw |