| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Andres Freund <andres(at)anarazel(dot)de>, 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:02:30 |
| Message-ID: | CA+TgmoZwkZmuVFT6M5kUpyRmceZ_MGN=MsbWpo=HTuE+be==jg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-committers pgsql-hackers |
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?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-06-20 16:14:00 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| Previous Message | Stephen Frost | 2019-06-20 12:52:11 | Re: UCT (Re: pgsql: Update time zone data files to tzdata release 2019a.) |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2019-06-20 16:05:19 | Re: check_recovery_target_lsn() does a PG_CATCH without a throw |
| Previous Message | Andres Freund | 2019-06-20 16:02:20 | Re: benchmarking Flex practices |