Remove dubious warning message from SQL/JSON functions
There was a warning that FORMAT JSON has no effect on json/jsonb
types, which is true, but it's not clear why we should issue a warning
about it. The SQL standard does not say anything about this, which
should generally govern the behavior
Remove dubious warning message from SQL/JSON functions
There was a warning that FORMAT JSON has no effect on json/jsonb
types, which is true, but it's not clear why we should issue a warning
about it. The SQL standard does not say anything about this, which
should generally govern the behavior
pg_upgrade: Improve style of a few verbose messages
Author: Peter Smith
Reviewed-by: Daniel Gustafsson
Discussion:
https://postgr.es/m/cahut+puob4buwkyaja_nktryaocky6w3zyk5pin305r7mns...@mail.gmail.com
Branch
--
master
Details
---
Fix format if entry in wait_event_names.txt
The entry LockManager had two successive whitespaces between two words.
This is not an actual bug, but let's be clean. Thinko in fa88928.
Reported-by: Masahiro Ikeda
Author: Bertrand Drouvot
Discussion:
Add a few recent commits to .git-blame-ignore-revs.
Reviewed-by: Peter Geoghegan
Discussion: https://postgr.es/m/20230815203109.GA2596919%40nathanxps13
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/0df7d1da40e3e639739eacccf3bca99a81803da7
Modified Files
On Thu, Aug 17, 2023 at 11:41 AM John Naylor
wrote:
>
>
> On Wed, Aug 16, 2023 at 5:17 PM John Naylor
wrote:
> >
> > Split out tiebreaker comparisons from comparetup_* functions
>
> Hammerkop is getting OOM errors with this change. Most grand totals in
the memory context stats show between 1 and
