From: | Noah Misch <noah(at)leadboat(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Vik Fearing <vik(at)postgresfriends(dot)org>, Thomas Munro <thomas(dot)munro(at)gmail(dot)com>, Petr Fedorov <petr(dot)fedorov(at)phystech(dot)edu>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch |
Date: | 2021-06-06 06:33:31 |
Message-ID: | 20210606063331.GC297923@rfd.leadboat.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Tue, Nov 03, 2020 at 07:22:14PM -0500, Tom Lane wrote:
> I feel like this is committable at this point --- any objections?
(This became commit 40c24bf, "Improve our ability to regurgitate SQL-syntax
function calls.")
> --- a/src/backend/nodes/equalfuncs.c
> +++ b/src/backend/nodes/equalfuncs.c
> @@ -2369,11 +2369,12 @@ _equalFuncCall(const FuncCall *a, const FuncCall *b)
> + COMPARE_SCALAR_FIELD(funcformat);
equalfuncs.c has been using COMPARE_COERCIONFORM_FIELD() to ignore differences
in fields of this type. Does this spot have cause to depart from the pattern?
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-06-06 14:37:58 | Re: Since '2001-09-09 01:46:40'::timestamp microseconds are lost when extracting epoch |
Previous Message | Noah Misch | 2021-06-05 21:31:28 | Re: BUG #16961: Could not access status of transaction |
From | Date | Subject | |
---|---|---|---|
Next Message | Julien Rouhaud | 2021-06-06 06:50:19 | Re: Hook for extensible parsing. |
Previous Message | vignesh C | 2021-06-06 06:25:18 | Re: Identify missing publications from publisher while create/alter subscription. |