Re: DecodeInterval fixes

From: Jacob Champion <jchampion(at)timescale(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>
Cc: jreidthompson(at)nc(dot)rr(dot)com, Joseph Koshakow <koshy44(at)gmail(dot)com>, Gurjeet Singh <gurjeet(at)singh(dot)im>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: DecodeInterval fixes
Date: 2023-08-22 16:58:18
Message-ID: CAAWbhmgffa8M04oOt=O1wT=DY_h3Wu3+gvMES=4vTh18DYnzwg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, Aug 21, 2023 at 10:39 PM Michael Paquier <michael(at)paquier(dot)xyz> wrote:
> 0002 and 0003 make this stuff fail, but isn't there a risk that this
> breaks applications that relied on these accidental behaviors?
> Assuming that this is OK makes me nervous.

I wouldn't argue for backpatching, for sure, but I guess I saw this as
falling into the same vein as 5b3c5953 and bcc704b52 which were
already committed.

--Jacob

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Nathan Bossart 2023-08-22 17:11:10 Re: should frontend tools use syncfs() ?
Previous Message Ashutosh Bapat 2023-08-22 16:07:22 Re: Oversight in reparameterize_path_by_child leading to executor crash