Stabilize streaming tests in test_decoding.
We have some streaming tests that rely on the size of changes which can
fail if there are additional changes like invalidation messages by
background activity like auto analyze. Avoid such failures by increasing
autovacuum_naptime to a reasonably high va
Stabilize streaming tests in test_decoding.
We have some streaming tests that rely on the size of changes which can
fail if there are additional changes like invalidation messages by
background activity like auto analyze. Avoid such failures by increasing
autovacuum_naptime to a reasonably high va
Doc: use "an SQL" consistently rather than "a SQL"
Similarly to what was done in 04539e73f, we standardized on SQL being
pronounced "es-que-ell" rather than "sequel" in our documentation.
Two inconsistencies have crept in during the v15 cycle. The others
existed before but were missed in 04539e7
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Fix breakage in AlterFunction().
An ALTER FUNCTION command that tried to update both the function's
proparallel property and its proconfig list failed to do the former,
because it stored the new proparallel value into a tuple that was
no longer the interesting one. Carelessness in 7aea8e4f2.
(I
Remove duplicated word in comment of basebackup.c
Oversight in 39969e2.
Author: Martín Marqués
Discussion:
https://postgr.es/m/CABeG9LviA01oHC5h=ksLUuhMyXxmZR_tftRq6q3341CMT=j=4...@mail.gmail.com
Branch
--
master
Details
---
https://git.postgresql.org/pg/commitdiff/83cca409edf276cfbd2f
Fix extract epoch from interval calculation
The new numeric code for extract epoch from interval accidentally
truncated the DAYS_PER_YEAR value to an integer, leading to results
that mismatched the floating-point interval_part calculations.
The commit a2da77cdb4661826482ebf2ddba1f953bc74afe4 that
Fix extract epoch from interval calculation
The new numeric code for extract epoch from interval accidentally
truncated the DAYS_PER_YEAR value to an integer, leading to results
that mismatched the floating-point interval_part calculations.
The commit a2da77cdb4661826482ebf2ddba1f953bc74afe4 that
On Tue, Apr 19, 2022 at 08:57:23PM +0200, Daniel Gustafsson wrote:
> > On 19 Apr 2022, at 16:24, Tom Lane wrote:
>
> > It's bothered the neatnik in me for a long time, so I'm happy to
> > make it happen if there are not objections.
>
> Mildly on-topic: Has the topic of a pgindent like process fo
> On 19 Apr 2022, at 16:24, Tom Lane wrote:
> It's bothered the neatnik in me for a long time, so I'm happy to
> make it happen if there are not objections.
Mildly on-topic: Has the topic of a pgindent like process for docs been
discussed at some point? The archives didn't turn up anything for m
Peter Eisentraut writes:
> On 16.04.22 22:26, Tom Lane wrote:
>> I'm not quite sure what's the point of retail fixes. I could
>> get behind removing*all* these occurrences, and then adjusting
>> .gitattributes so that git bleats about introducing new ones.
>> Other folks might find that a little
On 16.04.22 22:26, Tom Lane wrote:
Hmm ... by my count there are still 245 lines with trailing spaces
in the *.sgml files. (Most but not all are from copied-n-pasted
psql output.)
I'm not quite sure what's the point of retail fixes. I could
get behind removing*all* these occurrences, and then
> On 16 Apr 2022, at 22:26, Tom Lane wrote:
> I'm not quite sure what's the point of retail fixes. I could
> get behind removing *all* these occurrences, and then adjusting
> .gitattributes so that git bleats about introducing new ones.
> Other folks might find that a little too obsessive-compul
Fix aggregate logging of pgbench.
Remove meaningless "failures" column from the aggregate logging. It
was just a sum of "serialization failures" and "deadlock failures".
Pointed out by Tom Lane. Patch reviewed by Fabien COELHO.
Discussion: https://postgr.es/m/4183048.1649536705%40sss.pgh.pa.us
B
18 matches
Mail list logo
