| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Michael Paquier <michael(at)paquier(dot)xyz>, Vik Fearing <vik(at)postgresfriends(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Missing grammar production for WITH TIES |
| Date: | 2020-05-19 15:39:08 |
| Message-ID: | 20200519153908.GA17489@alvherre.pgsql |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 2020-May-19, Tom Lane wrote:
> Yeah, that would have been better per project protocol: if a tarball
> re-wrap becomes necessary then it would be messy not to include this
> change along with fixing whatever urgent bug there might be.
>
> However, I thought the case for delaying this fix till post-wrap was kind
> of thin anyway, so if that does happen I won't be too fussed about it.
> Otherwise I would've said something earlier on this thread.
In the end, it's a judgement call. In this case, my assessment was that
the risk was small enough that I could push after I saw the tarballs
announced. In other cases I've judged differently and waited for
longer. If the fix had been even simpler, I would have pushed it right
away, but my confidence with grammar changes is not as high as I would
like.
--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashwin Agrawal | 2020-05-19 15:56:13 | Re: SyncRepLock acquired exclusively in default configuration |
| Previous Message | Tom Lane | 2020-05-19 15:34:57 | Re: Extension ownership and misuse of SET ROLE/SET SESSION AUTHORIZATION |